From: Shreyansh Jain <shreyansh.jain@nxp.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev@dpdk.org, bruce.richardson@intel.com, thomas@monjalon.net,
stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v2 02/10] bus/dpaa: fix the BE compilation issue
Date: Thu, 1 Mar 2018 17:52:15 +0530 [thread overview]
Message-ID: <CAJ5mUsWTr1zG9fQiBZ0YD1zt8g7m3fJjT+_SXL2V4u-jmq0Wcg@mail.gmail.com> (raw)
In-Reply-To: <1519889597-5805-3-git-send-email-hemant.agrawal@nxp.com>
On Thu, Mar 1, 2018 at 1:03 PM, Hemant Agrawal <hemant.agrawal@nxp.com> wrote:
>
> The array pointers were used without index.
>
> Fixes: b9083ea5e084 ("net/dpaa: further push mode optimizations")
> Cc: stable@dpdk.org
>
> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> ---
> drivers/bus/dpaa/base/qbman/qman.c | 5 +++--
> drivers/bus/dpaa/base/qbman/qman_driver.c | 5 +----
> 2 files changed, 4 insertions(+), 6 deletions(-)
>
Acked-by: Shreyansh Jain <shreyansh.jain@nxp.com>
next prev parent reply other threads:[~2018-03-01 12:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1519752352-15442-1-git-send-email-hemant.agrawal@nxp.com>
2018-02-27 17:25 ` [dpdk-stable] [PATCH 1/7] event/dpaa: fix include header Hemant Agrawal
[not found] ` <1519889597-5805-1-git-send-email-hemant.agrawal@nxp.com>
2018-03-01 7:33 ` [dpdk-stable] [PATCH v2 01/10] " Hemant Agrawal
2018-03-01 7:33 ` [dpdk-stable] [PATCH v2 02/10] bus/dpaa: fix the BE compilation issue Hemant Agrawal
2018-03-01 12:22 ` Shreyansh Jain [this message]
[not found] ` <1521014166-3201-1-git-send-email-hemant.agrawal@nxp.com>
2018-03-14 7:55 ` [dpdk-stable] [PATCH v3 01/10] event/dpaa: fix include header Hemant Agrawal
2018-03-14 7:55 ` [dpdk-stable] [PATCH v3 02/10] bus/dpaa: fix the BE compilation issue 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=CAJ5mUsWTr1zG9fQiBZ0YD1zt8g7m3fJjT+_SXL2V4u-jmq0Wcg@mail.gmail.com \
--to=shreyansh.jain@nxp.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.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).