From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Zhihong Wang <zhihong.wang@intel.com>
Cc: dev@dpdk.org, bruce.richardson@intel.com, john.mcnamara@intel.com
Subject: Re: [dpdk-dev] [PATCH v3] doc: virtio PMD Rx/Tx callbacks
Date: Mon, 4 Jul 2016 10:56:37 +0800 [thread overview]
Message-ID: <20160704025637.GT2831@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <1467343681-91812-1-git-send-email-zhihong.wang@intel.com>
On Thu, Jun 30, 2016 at 11:28:01PM -0400, Zhihong Wang wrote:
> This patch explains current virtio PMD Rx/Tx callbacks, to help understand
> what's the difference, and how to enable the right ones.
>
> Signed-off-by: Zhihong Wang <zhihong.wang@intel.com>
> Acked-by: John McNamara <john.mcnamara@intel.com>
Applied to dpdk-next-virtio.
> --------------
> Changes in v3:
However, this is still wrong. It must start with 3 dashes, ---.
$ man git am
The patch is expected to be inline, directly following the
message. Any line that is of the form:
· three-dashes and end-of-line, or
· a line that begins with "diff -", or
· a line that begins with "Index: "
is taken as the beginning of a patch, and the commit log message
is terminated before the first occurrence of such a line.
This is just a note; I have fixed it while apply.
--yliu
next prev parent reply other threads:[~2016-07-04 2:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 3:55 [dpdk-dev] [PATCH] doc: virtio pmd versions Zhihong Wang
2016-06-09 12:35 ` Mcnamara, John
2016-06-09 12:52 ` Richardson, Bruce
2016-06-09 12:56 ` Mcnamara, John
2016-06-15 6:59 ` Wang, Zhihong
2016-06-14 23:53 ` [dpdk-dev] [PATCH v2] " Zhihong Wang
2016-06-24 16:03 ` Mcnamara, John
2016-06-29 3:27 ` Yuanhan Liu
2016-07-01 3:28 ` [dpdk-dev] [PATCH v3] doc: virtio PMD Rx/Tx callbacks Zhihong Wang
2016-07-04 2:56 ` Yuanhan Liu [this message]
2016-07-04 3:00 ` Wang, Zhihong
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=20160704025637.GT2831@yliu-dev.sh.intel.com \
--to=yuanhan.liu@linux.intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--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).