From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Krauz, Pavel" <Pavel.Krauz@anritsu.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] fix mbuf->port for eth_af_packet
Date: Wed, 9 Dec 2015 14:23:56 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2023FFD46@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <25CBA98BE75C5B44BD931C7C107685EDC090AA53@lut-exc-008.main.intgin.net>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Krauz, Pavel
> Sent: Wednesday, December 9, 2015 2:10 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] fix mbuf->port for eth_af_packet
>
> Hello,
> Here goes patch for DPDK 2.2.0.rc3 that fixes reported port number in mbuf
> when eth_af_packet PMD is used.
Hi Pavel,
Thanks for that. Could you resubmit the patch with a signoff line and in a
git diff format. See the draft Contributors Guide:
http://dpdk.org/dev/patchwork/patch/9019/
Regards,
John.
--
next prev parent reply other threads:[~2015-12-09 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 14:10 Krauz, Pavel
2015-12-09 14:23 ` Mcnamara, John [this message]
2015-12-09 14:46 ` Krauz, Pavel
2015-12-09 15:03 ` Mcnamara, John
2015-12-09 15:14 ` 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=B27915DBBA3421428155699D51E4CFE2023FFD46@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=Pavel.Krauz@anritsu.com \
--cc=dev@dpdk.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).