From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>,
"dev@dpdk.org" <dev@dpdk.org>, Ray Kinsella <mdr@ashroe.eu>,
Neil Horman <nhorman@tuxdriver.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
Sachin Saxena <sachin.saxena@nxp.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] net/dpaa: fix public API port ID type
Date: Mon, 14 Sep 2020 18:37:07 +0100 [thread overview]
Message-ID: <2627f245-a051-212b-ca2f-88ebae19042a@intel.com> (raw)
In-Reply-To: <AM6PR04MB4456778B7B335C589D07F2B189540@AM6PR04MB4456.eurprd04.prod.outlook.com>
On 8/26/2020 6:15 AM, Hemant Agrawal wrote:
>> -----Original Message-----
>> From: Ferruh Yigit <ferruh.yigit@intel.com>
>> Sent: Tuesday, August 25, 2020 11:21 PM
>> To: dev@dpdk.org; Ray Kinsella <mdr@ashroe.eu>; Neil Horman
>> <nhorman@tuxdriver.com>; John McNamara <john.mcnamara@intel.com>;
>> Marko Kovacevic <marko.kovacevic@intel.com>; Hemant Agrawal
>> <hemant.agrawal@nxp.com>; Sachin Saxena <sachin.saxena@nxp.com>
>> Cc: Ferruh Yigit <ferruh.yigit@intel.com>; stable@dpdk.org
>> Subject: [PATCH v2] net/dpaa: fix public API port ID type
>>
>> Updating the type for 'port' variable from 'uint8_t' to 'uint16_t'.
>>
>> Fixes: 8c3495f5d2dd ("net/dpaa: support loopback API")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2020-09-14 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 21:52 [dpdk-dev] [PATCH v20.11] net/dpaa: fix public API port ID type Ferruh Yigit
2020-08-25 17:51 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2020-08-26 5:15 ` Hemant Agrawal
2020-09-14 17:37 ` Ferruh Yigit [this message]
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=2627f245-a051-212b-ca2f-88ebae19042a@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=mdr@ashroe.eu \
--cc=nhorman@tuxdriver.com \
--cc=sachin.saxena@nxp.com \
--cc=stable@dpdk.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.