From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "rahul.lakkireddy@chelsio.com" <rahul.lakkireddy@chelsio.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Kumar Sanghvi <kumaras@chelsio.com>,
Felix Marti <felix@chelsio.com>,
Nirranjan Kirubaharan <nirranjan@chelsio.com>,
sys_stv <sys_stv@intel.com>
Subject: Re: [dpdk-dev] |ERROR| pw 9018 ethdev: add a missing sanity check for nb_tx_desc during txq setup
Date: Fri, 20 Nov 2015 14:10:00 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2023C0A0D@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <20151120133710.GA30609@scalar.blr.asicdesigners.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Rahul Lakkireddy
> Sent: Friday, November 20, 2015 1:37 PM
> To: dev@dpdk.org
> Cc: Felix Marti; Kumar Sanghvi; Nirranjan Kirubaharan
> Subject: Re: [dpdk-dev] |ERROR| pw 9018 ethdev: add a missing sanity check
> for nb_tx_desc during txq setup
>
> Hi all,
>
> I received this auto email regarding 'Unexpected Packets Drop' and it is
> referring to my patch. I don't think I've changed anything that could
> cause this. Kindly advise.
Hi,
It may be a false positive or it may be an issue.
For what it is worth, I submitted a patch just after yours that passed:
http://dpdk.org/ml/archives/test-report/2015-November/thread.html
CCing sys_stv and Waterman to see if this test can be rerun to double-check.
John.
--
next prev parent reply other threads:[~2015-11-20 14:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <edcf24$hvv9db@FMSMGA003.fm.intel.com>
2015-11-20 13:37 ` Rahul Lakkireddy
2015-11-20 14:10 ` Mcnamara, John [this message]
2015-11-23 7:06 ` Liu, Yong
2015-11-23 7:27 ` Yuanhan Liu
2015-11-23 7:36 ` Liu, Yong
2015-11-23 7:41 ` Yuanhan Liu
2015-11-23 9:05 ` Liu, Yong
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=B27915DBBA3421428155699D51E4CFE2023C0A0D@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=felix@chelsio.com \
--cc=kumaras@chelsio.com \
--cc=nirranjan@chelsio.com \
--cc=rahul.lakkireddy@chelsio.com \
--cc=sys_stv@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).