DPDK patches and discussions
 help / color / mirror / Atom feed
From: Nipun Gupta <nipun.gupta@nxp.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>,
	Sachin Saxena <sachin.saxena@nxp.com>
Subject: Re: [dpdk-dev] [PATCH] net/dpaa2: set port in the mbuf
Date: Wed, 9 Oct 2019 11:26:10 +0000	[thread overview]
Message-ID: <VI1PR04MB44805CCFF6246A918F21BAEEE6950@VI1PR04MB4480.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <39a98ca6-48c3-7b89-1b30-fb451454a0b9@intel.com>



> -----Original Message-----
> From: Ferruh Yigit <ferruh.yigit@intel.com>
> Sent: Tuesday, October 8, 2019 3:09 PM
> To: Nipun Gupta <nipun.gupta@nxp.com>; dev@dpdk.org
> Cc: Hemant Agrawal <hemant.agrawal@nxp.com>; Sachin Saxena
> <sachin.saxena@nxp.com>
> Subject: Re: [PATCH] net/dpaa2: set port in the mbuf
> 
> On 10/4/2019 12:01 PM, Nipun Gupta wrote:
> > This patch sets the port in mbuf for all the scenarios within
> > fd to mbuf API
> 
> Hi Nipun,
> 
> What is the impact of not setting 'port' field for all the scenarios? If it
> breaks something, do you want to backport this patch? By converting it to a
> fix
> patch..

Hi Ferruh,

You are right. It breaks event scenarios - parallel, atomic and ordered.
There are multiple commits involved. Ill add Fixes and resend.

Thanks

> 
> >
> > Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com>
> > Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>


  reply	other threads:[~2019-10-09 11:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-04 11:01 Nipun Gupta
2019-10-08  9:38 ` Ferruh Yigit
2019-10-09 11:26   ` Nipun Gupta [this message]
2019-10-09 11:13 ` [dpdk-dev] [PATCH v2] " Nipun Gupta
2019-10-14  9:36   ` Ferruh Yigit

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=VI1PR04MB44805CCFF6246A918F21BAEEE6950@VI1PR04MB4480.eurprd04.prod.outlook.com \
    --to=nipun.gupta@nxp.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=sachin.saxena@nxp.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).