From: Akhil Goyal <akhil.goyal@nxp.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>, Nipun Gupta <nipun.gupta@nxp.com>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH 01/37] bus/fslmc: fix getting the FD error
Date: Wed, 27 May 2020 18:07:32 +0000 [thread overview]
Message-ID: <VI1PR04MB316826B11738BE1C5A3F9438E6B10@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20200527132326.1382-2-hemant.agrawal@nxp.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Hemant Agrawal
> Sent: Wednesday, May 27, 2020 6:53 PM
> To: dev@dpdk.org; ferruh.yigit@intel.com
> Cc: stable@dpdk.org; Nipun Gupta <nipun.gupta@nxp.com>
> Subject: [dpdk-dev] [PATCH 01/37] bus/fslmc: fix getting the FD error
>
> From: Nipun Gupta <nipun.gupta@nxp.com>
>
> Fix the incorrect register for getting error
>
> Fixes: 03e36408b9fb ("bus/fslmc: add macros required by QDMA for FLE and FD")
> Cc: stable@dpdk.org
>
> Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com>
> ---
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
next prev parent reply other threads:[~2020-05-27 18:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200527132326.1382-1-hemant.agrawal@nxp.com>
2020-05-27 13:22 ` [dpdk-stable] " Hemant Agrawal
2020-05-27 18:07 ` Akhil Goyal [this message]
2020-05-27 13:22 ` [dpdk-stable] [PATCH 02/37] net/dpaa: fix fd offset data type Hemant Agrawal
2020-05-27 18:08 ` [dpdk-stable] [dpdk-dev] " Akhil Goyal
[not found] ` <20200707092244.12791-1-hemant.agrawal@nxp.com>
2020-07-07 9:22 ` [dpdk-stable] [PATCH v2 01/29] bus/fslmc: fix getting the FD error Hemant Agrawal
2020-07-07 9:22 ` [dpdk-stable] [PATCH v2 02/29] net/dpaa: fix fd offset data type Hemant Agrawal
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=VI1PR04MB316826B11738BE1C5A3F9438E6B10@VI1PR04MB3168.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=nipun.gupta@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 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).