From: "Ouyang, Changchun" <changchun.ouyang@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Stephen Hemminger <shemming@brocade.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/2] virtio: fixes for 2.1-rc1
Date: Tue, 21 Jul 2015 05:00:26 +0000 [thread overview]
Message-ID: <F52918179C57134FAEC9EA62FA2F962511C0EBBE@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1437417646-11221-1-git-send-email-stephen@networkplumber.org>
> -----Original Message-----
> From: Stephen Hemminger [mailto:stephen@networkplumber.org]
> Sent: Tuesday, July 21, 2015 2:41 AM
> To: Ouyang, Changchun
> Cc: dev@dpdk.org; Stephen Hemminger
> Subject: [PATCH v2 0/2] virtio: fixes for 2.1-rc1
I think v2 here should be v3, as you have already a v2.
>
> From: Stephen Hemminger <shemming@brocade.com>
>
> This integrates my change and earlier change by Ouyang Changchun into one
> fix. And second patch is minor stuff found while reviewing.
>
> Stephen Hemminger (2):
> virtio: fix queue size and number of descriptors
> virtio: small cleanups
>
> drivers/net/virtio/virtio_ethdev.c | 24 +++++++-----------------
> drivers/net/virtio/virtio_ethdev.h | 2 +-
> drivers/net/virtio/virtio_rxtx.c | 2 +-
> 3 files changed, 9 insertions(+), 19 deletions(-)
>
> --
> 2.1.4
next prev parent reply other threads:[~2015-07-21 5:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 18:40 Stephen Hemminger
2015-07-20 18:40 ` [dpdk-dev] [PATCH v2 1/2] virtio: fix queue size and number of descriptors Stephen Hemminger
2015-07-21 5:06 ` Ouyang, Changchun
2015-07-22 8:55 ` Thomas Monjalon
2015-07-20 18:40 ` [dpdk-dev] [PATCH v2 2/2] virtio: small cleanups Stephen Hemminger
2015-07-21 4:57 ` Ouyang, Changchun
2015-07-21 5:00 ` Ouyang, Changchun [this message]
2015-07-22 8:59 ` [dpdk-dev] [PATCH v2 0/2] virtio: fixes for 2.1-rc1 Thomas Monjalon
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=F52918179C57134FAEC9EA62FA2F962511C0EBBE@shsmsx102.ccr.corp.intel.com \
--to=changchun.ouyang@intel.com \
--cc=dev@dpdk.org \
--cc=shemming@brocade.com \
--cc=stephen@networkplumber.org \
/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).