From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Ferruh Yigit <ferruh.yigit@xilinx.com>,
Gagandeep Singh <G.Singh@nxp.com>, "dev@dpdk.org" <dev@dpdk.org>,
"Sachin Saxena (OSS)" <sachin.saxena@oss.nxp.com>
Cc: Rohit Raj <rohit.raj@nxp.com>
Subject: RE: [PATCH 1/4] net/dpaa2: update mc to 10.32
Date: Tue, 10 May 2022 12:53:40 +0000 [thread overview]
Message-ID: <AS8PR04MB9064A09D0AE4E30AF51BE27E89C99@AS8PR04MB9064.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <8205a994-60ec-8ab7-1bef-08510fe5719a@xilinx.com>
Hi Ferruh,
I am ok for it.
You can add:
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> -----Original Message-----
> From: Ferruh Yigit <ferruh.yigit@xilinx.com>
> Sent: Tuesday, May 10, 2022 6:22 PM
> To: Gagandeep Singh <G.Singh@nxp.com>; dev@dpdk.org; Hemant Agrawal
> <hemant.agrawal@nxp.com>; Sachin Saxena (OSS)
> <sachin.saxena@oss.nxp.com>
> Cc: Rohit Raj <rohit.raj@nxp.com>
> Subject: Re: [PATCH 1/4] net/dpaa2: update mc to 10.32
> Importance: High
>
> On 4/22/2022 5:57 AM, Gagandeep Singh wrote:
> > From: Rohit Raj <rohit.raj@nxp.com>
> >
> > Updating the management complex to version 10.32
> >
> > Signed-off-by: Rohit Raj <rohit.raj@nxp.com>
> > Signed-off-by: Gagandeep Singh <g.singh@nxp.com>
>
> Hi Hemant, Sachin,
>
> The set looks good to me, do you have any comment/review?
next prev parent reply other threads:[~2022-05-10 12:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 4:57 Gagandeep Singh
2022-04-22 4:57 ` [PATCH 2/4] net/dpaa2: support mempool debug Gagandeep Singh
2022-04-22 4:57 ` [PATCH 3/4] net/dpaa2: support ESP in packet type parsing Gagandeep Singh
2022-04-22 4:57 ` [PATCH 4/4] net/dpaa: fix ethernet event queue de-attach Gagandeep Singh
2022-05-10 12:51 ` [PATCH 1/4] net/dpaa2: update mc to 10.32 Ferruh Yigit
2022-05-10 12:53 ` Hemant Agrawal [this message]
2022-05-10 16:33 ` 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=AS8PR04MB9064A09D0AE4E30AF51BE27E89C99@AS8PR04MB9064.eurprd04.prod.outlook.com \
--to=hemant.agrawal@nxp.com \
--cc=G.Singh@nxp.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@xilinx.com \
--cc=rohit.raj@nxp.com \
--cc=sachin.saxena@oss.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).