From: "Ouyang, Changchun" <changchun.ouyang@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] [PMD] [VHOST] Revert unnecessary definition and fix wrong referring in user space vhost zero copy patches
Date: Tue, 20 May 2014 01:14:53 +0000 [thread overview]
Message-ID: <F52918179C57134FAEC9EA62FA2F9625117A9950@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1478243.AGf3d0Vu1X@xps13>
Hi Thomas,
Fine, I will do it.
One more question:
You have comments as follow:
The title was "[PATCH 0/3] [PMD] [VHOST] *** Support zero copy RX/TX in user space vhost ***"
It should be "[PATCH v2 0/3] Support zero copy RX/TX in user space vhost"
So "[PMD] [VHOST]" in the title should be removed in the cover letter, right?
And in each separate patch letter, it could use "ixgbe:" or "examples/vhost:", instead of "[PMD] [VHOST]"
Is it right?
Thanks
Changchun
-----Original Message-----
From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
Sent: Tuesday, May 20, 2014 12:00 AM
To: Ouyang, Changchun
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] [PMD] [VHOST] Revert unnecessary definition and fix wrong referring in user space vhost zero copy patches
Hi Changchun,
2014-05-19 23:09, Ouyang Changchun:
> 1. Revert the change of metadata macro definition for referring to
> headroom space in mbuf; 2. Fix wrongly referring to RX queues number
> in TX queues start/stop function.
>
> Signed-off-by: Ouyang Changchun <changchun.ouyang@intel.com>
You are fixing commits which are not yet applied.
Please merge and re-send the whole serie by suffixing with "v2".
The title was "[PATCH 0/3] [PMD] [VHOST] *** Support zero copy RX/TX in user space vhost ***"
It should be "[PATCH v2 0/3] Support zero copy RX/TX in user space vhost"
Other notes:
- please split API and ixgbe changes
- set a significant title to each patch
- use prefixes like "ethdev:", "ixgbe:" or "examples/vhost:"
In general, this page is a good help:
http://dpdk.org/dev#send
Thanks
--
Thomas
next prev parent reply other threads:[~2014-05-20 1:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 15:09 Ouyang Changchun
2014-05-19 16:00 ` Thomas Monjalon
2014-05-20 1:14 ` Ouyang, Changchun [this message]
2014-05-22 15:28 ` Thomas Monjalon
2014-05-22 15:41 ` Ouyang, Changchun
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=F52918179C57134FAEC9EA62FA2F9625117A9950@shsmsx102.ccr.corp.intel.com \
--to=changchun.ouyang@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).