patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: stable@dpdk.org, tiwei.bie@intel.com, yliu@fridaylinux.org,
	ferruh.yigit@intel.com, victork@redhat.com,
	olivier.matz@6wind.com, jianfeng.tan@intel.com, dev@dpdk.org,
	zhihong.wang@intel.com, qian.q.xu@intel.com, lei.a.yao@intel.com
Subject: Re: [dpdk-stable] [PATCH v2 0/3] Vhost & Virtio fixes for v18.02
Date: Tue, 13 Feb 2018 18:45:12 +0100	[thread overview]
Message-ID: <2419328.12RB65Uumv@xps> (raw)
In-Reply-To: <20180212154612.5297-1-maxime.coquelin@redhat.com>

12/02/2018 16:46, Maxime Coquelin:
> The second revision of this series includes Olivier's patch as first
> patch in order to ease Thomas job when applying.
> 
> Patch 2 rewords the commit message with detailed informations
> provided by Tiwei and olivier (Thanks!). It also moves call to
> virtio_rxq_vec_setup() and removes virtqueue_enqueue_recv_refill_simple()
> as no more used.
> 
> Maxime Coquelin (2):
>   virtio: fix resuming port with rx vector path
>   vhost: don't take access_lock on VHOST_USER_RESET_OWNER
> 
> Olivier Matz (1):
>   net/virtio: fix mbuf data offset for simple Rx function

Applied, thanks

      parent reply	other threads:[~2018-02-13 17:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-12 15:46 Maxime Coquelin
2018-02-12 15:46 ` [dpdk-stable] [PATCH v2 1/3] net/virtio: fix mbuf data offset for simple Rx function Maxime Coquelin
2018-02-13  8:53   ` [dpdk-stable] [dpdk-dev] " Maxime Coquelin
2018-02-12 15:46 ` [dpdk-stable] [PATCH v2 2/3] virtio: fix resuming port with rx vector path Maxime Coquelin
2018-02-12 15:46 ` [dpdk-stable] [PATCH v2 3/3] vhost: don't take access_lock on VHOST_USER_RESET_OWNER Maxime Coquelin
2018-02-13 17:45 ` Thomas Monjalon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2419328.12RB65Uumv@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jianfeng.tan@intel.com \
    --cc=lei.a.yao@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=olivier.matz@6wind.com \
    --cc=qian.q.xu@intel.com \
    --cc=stable@dpdk.org \
    --cc=tiwei.bie@intel.com \
    --cc=victork@redhat.com \
    --cc=yliu@fridaylinux.org \
    --cc=zhihong.wang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).