From: Ruifeng Wang <Ruifeng.Wang@arm.com>
To: Ruifeng Wang <Ruifeng.Wang@arm.com>,
"Ajit Khaparde (ajit.khaparde@broadcom.com)"
<ajit.khaparde@broadcom.com>,
"somnath.kotur@broadcom.com" <somnath.kotur@broadcom.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
nd <nd@arm.com>, Kathleen Capella <Kathleen.Capella@arm.com>,
nd <nd@arm.com>
Subject: RE: [PATCH 2/2] net/bnxt: remove some dead code
Date: Wed, 11 May 2022 06:08:44 +0000 [thread overview]
Message-ID: <AS8PR08MB7080CDDB20AA24A8BA7096CD9EC89@AS8PR08MB7080.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <20220510063118.449216-3-ruifeng.wang@arm.com>
> -----Original Message-----
> From: Ruifeng Wang <ruifeng.wang@arm.com>
> Sent: Tuesday, May 10, 2022 2:31 PM
> To: Ajit Khaparde (ajit.khaparde@broadcom.com)
> <ajit.khaparde@broadcom.com>; somnath.kotur@broadcom.com
> Cc: dev@dpdk.org; Honnappa Nagarahalli
> <Honnappa.Nagarahalli@arm.com>; nd <nd@arm.com>; Ruifeng Wang
> <Ruifeng.Wang@arm.com>; Kathleen Capella <Kathleen.Capella@arm.com>
> Subject: [PATCH 2/2] net/bnxt: remove some dead code
>
> Removed some macros that were defined but not used in this driver.
> As a result, rte_smp_xx occurrence is removed from this driver.
>
> Signed-off-by: Ruifeng Wang <ruifeng.wang@arm.com>
> Reviewed-by: Kathleen Capella <kathleen.capella@arm.com>
> ---
> drivers/net/bnxt/bnxt_cpr.h | 14 --------------
> 1 file changed, 14 deletions(-)
>
The CI failures reported by ci/intel-Testing seem to be irrelevant with this patch.
next prev parent reply other threads:[~2022-05-11 6:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 6:31 [PATCH 0/2] atomic changes Ruifeng Wang
2022-05-10 6:31 ` [PATCH 1/2] net/bnxt: use compiler atomics for stats Ruifeng Wang
2022-05-10 6:31 ` [PATCH 2/2] net/bnxt: remove some dead code Ruifeng Wang
2022-05-11 6:08 ` Ruifeng Wang [this message]
2022-05-23 0:55 ` [PATCH 0/2] atomic changes Ajit Khaparde
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=AS8PR08MB7080CDDB20AA24A8BA7096CD9EC89@AS8PR08MB7080.eurprd08.prod.outlook.com \
--to=ruifeng.wang@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Kathleen.Capella@arm.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=nd@arm.com \
--cc=somnath.kotur@broadcom.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).