From: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] doc: Malicious Driver Detection not supported by ixgbe
Date: Mon, 29 Feb 2016 01:38:50 +0000 [thread overview]
Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC09090343623F@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20160226144104.GB21628@bricha3-MOBL3>
Hi Bruce,
> -----Original Message-----
> From: Richardson, Bruce
> Sent: Friday, February 26, 2016 10:41 PM
> To: Lu, Wenzhuo
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v2] doc: Malicious Driver Detection not
> supported by ixgbe
>
> On Fri, Feb 26, 2016 at 12:48:37PM +0800, Wenzhuo Lu wrote:
> > Announce that Malicious Driver Detection is not supported.
> >
> > V2:
> > *Rework the words.
> >
> > Signed-off-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
>
> Hi Wenzhuo,
>
> just for future reference, please put the V2,v3 etc. updates below the cut line "--
> -" so that they can be auto-stripped when applying the patch.
>
> /Bruce
Got it. Thanks for the reminder :)
>
> > ---
> > doc/guides/nics/ixgbe.rst | 20 ++++++++++++++++++++
> > doc/guides/rel_notes/release_16_04.rst | 23 +++++++++++++++++++++++
> > 2 files changed, 43 insertions(+)
> >
> <snip>
next prev parent reply other threads:[~2016-02-29 1:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 5:33 [dpdk-dev] [PATCH] " Wenzhuo Lu
2016-02-24 17:04 ` Stephen Hemminger
2016-02-25 1:13 ` Lu, Wenzhuo
2016-02-26 4:48 ` [dpdk-dev] [PATCH v2] " Wenzhuo Lu
2016-02-26 14:41 ` Bruce Richardson
2016-02-29 1:38 ` Lu, Wenzhuo [this message]
2016-03-06 22:24 ` Thomas Monjalon
2016-03-07 0:45 ` Lu, Wenzhuo
2016-03-07 5:28 ` [dpdk-dev] [PATCH v3] " Wenzhuo Lu
2016-03-07 20:57 ` Thomas Monjalon
2016-03-02 6:06 [dpdk-dev] [PATCH v2] " He, Shaopeng
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=6A0DE07E22DDAD4C9103DF62FEBC09090343623F@shsmsx102.ccr.corp.intel.com \
--to=wenzhuo.lu@intel.com \
--cc=bruce.richardson@intel.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).