DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	"xueqin.lin@intel.com" <xueqin.lin@intel.com>,
	"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
	"thomas@monjalon.net" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Yao, Lei A" <lei.a.yao@intel.com>,
	"Wang, FengqinX" <fengqinx.wang@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] app/testpmd: fix ether header size calculation
Date: Tue, 9 Apr 2019 21:59:29 +0100	[thread overview]
Message-ID: <f7220097-05ba-8222-e316-aff65979f7d8@intel.com> (raw)
Message-ID: <20190409205929.ikihoF6mzUPTZzDrStw2kgyZLdbG7lZJxvQH4jU5x7M@z> (raw)
In-Reply-To: <20190409094543.26751-1-pbhagavatula@marvell.com>

On 4/9/2019 10:45 AM, Pavan Nikhilesh Bhagavatula wrote:
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
> 
> Fix ether header size calculation in Tx only mode.
> 
> Coverity issue: 337684
> Fixes: 01b645dcff7f ("app/testpmd: move txonly prepare in separate function")
> 
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>

Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>

Applied to dpdk-next-net/master, thanks.


@lei, can you please confirm the txonly mode on next-net?

  parent reply	other threads:[~2019-04-09 20:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-08 10:13 [dpdk-dev] [PATCH] " Pavan Nikhilesh Bhagavatula
2019-04-08 10:13 ` Pavan Nikhilesh Bhagavatula
2019-04-08 11:57 ` Bruce Richardson
2019-04-08 11:57   ` Bruce Richardson
2019-04-08 12:28   ` [dpdk-dev] [EXT] " Pavan Nikhilesh Bhagavatula
2019-04-08 12:28     ` Pavan Nikhilesh Bhagavatula
2019-04-09  9:45 ` [dpdk-dev] [PATCH v2] " Pavan Nikhilesh Bhagavatula
2019-04-09  9:45   ` Pavan Nikhilesh Bhagavatula
2019-04-09 20:59   ` Ferruh Yigit [this message]
2019-04-09 20:59     ` Ferruh Yigit
2019-04-10  1:23     ` Yao, Lei A
2019-04-10  1:23       ` Yao, Lei A

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=f7220097-05ba-8222-e316-aff65979f7d8@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=fengqinx.wang@intel.com \
    --cc=jerinj@marvell.com \
    --cc=lei.a.yao@intel.com \
    --cc=pbhagavatula@marvell.com \
    --cc=thomas@monjalon.net \
    --cc=xueqin.lin@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).