From: Akhil Goyal <gakhil@marvell.com>
To: "Min Hu (Connor)" <humin29@huawei.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"nicolas.chautru@intel.com" <nicolas.chautru@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [EXT] [dpdk-dev] [PATCH v2] app/bbdev: fix wrong variable
Date: Wed, 5 May 2021 14:43:36 +0000 [thread overview]
Message-ID: <MW2PR18MB228482B72C4CF77CF3E5AABAD8599@MW2PR18MB2284.namprd18.prod.outlook.com> (raw)
In-Reply-To: <1619398619-58601-1-git-send-email-humin29@huawei.com>
> The logging should show context by printing the two variable which
> compared to each other. 'nb_harq_inputs', not 'nb_hard_outputs';
> 'nb_harq_outputs', not 'nb_hard_outputs'.
>
> This patch corrected misused variable.
>
> Fixes: d819c08327f3 ("app/bbdev: update for 5GNR")
> Cc: stable@dpdk.org
>
> Signed-off-by: Min Hu (Connor) <humin29@huawei.com>
> Acked-by: Nicolas Chautru <Nicolas.chautru@intel.com>
> ---
Applied to dpdk-next-crypto
Thanks.
parent reply other threads:[~2021-05-05 14:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1619398619-58601-1-git-send-email-humin29@huawei.com>]
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=MW2PR18MB228482B72C4CF77CF3E5AABAD8599@MW2PR18MB2284.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=humin29@huawei.com \
--cc=nicolas.chautru@intel.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).