From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: Ouyang Changchun
<changchun.ouyang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [PATCH] [PMD] [VHOST] Revert unnecessary definition and fix wrong referring in user space vhost zero copy patches
Date: Mon, 19 May 2014 18:00:13 +0200 [thread overview]
Message-ID: <1478243.AGf3d0Vu1X@xps13> (raw)
In-Reply-To: <1400512177-19315-1-git-send-email-changchun.ouyang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
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-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
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-19 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 15:09 [PATCH] [PMD] [VHOST] Revert unnecessary definition and fix wrong referring in user space vhost zero copy patches Ouyang Changchun
[not found] ` <1400512177-19315-1-git-send-email-changchun.ouyang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-05-19 16:00 ` Thomas Monjalon [this message]
2014-05-20 1:14 ` Ouyang, Changchun
[not found] ` <F52918179C57134FAEC9EA62FA2F9625117A9950-E2R4CRU6q/6iAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
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=1478243.AGf3d0Vu1X@xps13 \
--to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=changchun.ouyang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.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).