From: "Rao, Nikhil" <nikhil.rao@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>
Cc: stable@dpdk.org, dev@dpdk.org, nikhil.rao@intel.com
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] eventdev: fix eth port in eth Rx adapter internal function
Date: Sun, 3 Jun 2018 12:53:39 +0530 [thread overview]
Message-ID: <69458275-b99c-2d35-5fd8-400f93ccc164@intel.com> (raw)
In-Reply-To: <2762021.gLiFmiYqnl@xps>
On 5/25/2018 2:25 AM, Thomas Monjalon wrote:
> 23/05/2018 07:51, Jerin Jacob:
>> -----Original Message-----
>>> Date: Wed, 23 May 2018 02:36:42 +0530
>>> From: Nikhil Rao <nikhil.rao@intel.com>
>>> To: jerin.jacob@caviumnetworks.com
>>> CC: dev@dpdk.org, Nikhil Rao <nikhil.rao@intel.com>, stable@dpdk.org
>>> Subject: [PATCH] eventdev: fix eth port in eth Rx adapter internal function
>>> X-Mailer: git-send-email 1.8.3.1
>>>
>>> The dev_id parameter to fill_event_buffer() should be 16 bit,
>>> also rename to to eth_dev_id to avoid confusion with event device
>>> id elsewhere in the file.
>>>
>>> Fixes: c2189c907dd1 ("eventdev: make ethdev port identifiers 16-bit")
>>> Cc: stable@dpdk.org
>>> Signed-off-by: Nikhil Rao <nikhil.rao@intel.com>
>>
>> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Hi Jerin,
Can you please apply this patch to next-eventdev ?
Nikhil
>
> It doesn't look to be critical.
> So it is deferred to 18.08 (we minimize risks in -rc6).
>
>
>
next prev parent reply other threads:[~2018-06-03 7:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 21:06 [dpdk-dev] " Nikhil Rao
2018-05-23 5:51 ` Jerin Jacob
2018-05-24 20:55 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2018-06-03 7:23 ` Rao, Nikhil [this message]
2018-06-04 2:58 ` Jerin Jacob
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=69458275-b99c-2d35-5fd8-400f93ccc164@intel.com \
--to=nikhil.rao@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).