From: "Xing, Beilei" <beilei.xing@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "Wu, Jingjing" <jingjing.wu@intel.com>,
"Jastrzebski, MichalX K" <michalx.k.jastrzebski@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/4] i40e: fix coverity defects
Date: Tue, 5 Jul 2016 01:47:14 +0000 [thread overview]
Message-ID: <94479800C636CB44BD422CB454846E013ABC9A@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20160704135801.GE16932@bricha3-MOBL3>
Hi Bruce,
> -----Original Message-----
> From: Richardson, Bruce
> Sent: Monday, July 4, 2016 9:58 PM
> To: Xing, Beilei <beilei.xing@intel.com>
> Cc: Wu, Jingjing <jingjing.wu@intel.com>; Jastrzebski, MichalX K
> <michalx.k.jastrzebski@intel.com>; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH 0/4] i40e: fix coverity defects
>
> On Thu, Jun 30, 2016 at 03:34:16PM +0800, Beilei Xing wrote:
> > Fix some open coverity defects.
> >
> > Beilei Xing (4):
> > i40e: fix wrong operator
> > i40e: fix dereference before null check
> > i40e: fix out-of-bounds access
> > examples/tep_term: fix out-of-bounds access
> >
> > drivers/net/i40e/i40e_ethdev.c | 35 ++++++++++++++++++++---------
> -----
> > drivers/net/i40e/i40e_ethdev_vf.c | 7 +++++--
> > examples/tep_termination/vxlan_setup.c | 2 +-
> > 3 files changed, 27 insertions(+), 17 deletions(-)
> >
> > --
>
> Hi Beilei,
>
> thanks for the patches. Since these are coverity fixes, can you please do a V2
> with the coverity id's being fixed called out in the commit message. The
> format to use is:
>
> Coverity issue: xxxxx yyyyy ....
>
> just above the fixes line in the patch. [Use "git log" to see examples in other
> commits].
Thanks for guides:)
>
> Also, for convenience sake for myself and Thomas, can you include just the
> three i40e patches in one set - since those go to next-net tree - and submit
> the examples fix as a separate standalone patch to go in the main tree.
OK, no problem, will send v2 later.
>
> Thanks,
> /Bruce
next prev parent reply other threads:[~2016-07-05 1:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 7:34 Beilei Xing
2016-07-04 13:58 ` Bruce Richardson
2016-07-05 1:47 ` Xing, Beilei [this message]
2016-07-05 6:10 ` [dpdk-dev] [PATCH v2 0/3] " Beilei Xing
2016-07-05 6:10 ` [dpdk-dev] [PATCH v2 1/3] i40e: fix log error Beilei Xing
2016-07-05 13:24 ` Bruce Richardson
2016-07-05 6:10 ` [dpdk-dev] [PATCH v2 2/3] i40e: fix dereference before null check Beilei Xing
2016-07-05 13:24 ` Bruce Richardson
2016-07-05 6:10 ` [dpdk-dev] [PATCH v2 3/3] i40e: fix out-of-bounds access Beilei Xing
2016-07-05 13:26 ` Bruce Richardson
2016-07-06 2:00 ` Xing, Beilei
2016-07-08 15:23 ` Bruce Richardson
2016-07-08 15:33 ` [dpdk-dev] [PATCH v2 0/3] fix coverity defects Bruce Richardson
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=94479800C636CB44BD422CB454846E013ABC9A@SHSMSX101.ccr.corp.intel.com \
--to=beilei.xing@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.com \
--cc=michalx.k.jastrzebski@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).