From: Bruce Richardson <bruce.richardson@intel.com>
To: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] e1000: enable promiscuous and allmulticast support for VF
Date: Fri, 26 Feb 2016 17:28:34 +0000 [thread overview]
Message-ID: <20160226172834.GD28808@bricha3-MOBL3> (raw)
In-Reply-To: <6A0DE07E22DDAD4C9103DF62FEBC09090342ADB2@shsmsx102.ccr.corp.intel.com>
On Tue, Feb 16, 2016 at 12:43:38AM +0000, Lu, Wenzhuo wrote:
> Hi Yury,
>
> Acked-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
>
Applied to dpdk-next-net/rel_16_04
/Bruce
prev parent reply other threads:[~2016-02-26 17:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 14:46 [dpdk-dev] [PATCH] e1000: enable " Yury Kylulin
2015-06-15 15:09 ` Thomas Monjalon
2015-06-16 1:36 ` Lu, Wenzhuo
2015-07-14 0:59 ` Lu, Wenzhuo
2016-02-09 9:09 ` [dpdk-dev] [PATCH v2] e1000: enable promiscuous and " Yury Kylulin
2016-02-15 1:14 ` Lu, Wenzhuo
2016-02-15 10:44 ` Kylulin, Yury
2016-02-16 0:43 ` Lu, Wenzhuo
2016-02-26 17:28 ` Bruce Richardson [this message]
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=20160226172834.GD28808@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=wenzhuo.lu@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).