From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Ruifeng Wang <ruifeng.wang@arm.com>
Cc: Somnath Kotur <somnath.kotur@broadcom.com>,
dpdk-dev <dev@dpdk.org>,
Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
nd <nd@arm.com>
Subject: Re: [PATCH 0/2] atomic changes
Date: Sun, 22 May 2022 17:55:44 -0700 [thread overview]
Message-ID: <CACZ4nhuO-UmFKxdJbagsz8jgv=YMrnujBKzwo8qikh8X1twG=Q@mail.gmail.com> (raw)
In-Reply-To: <20220510063118.449216-1-ruifeng.wang@arm.com>
[-- Attachment #1: Type: text/plain, Size: 699 bytes --]
On Mon, May 9, 2022 at 11:31 PM Ruifeng Wang <ruifeng.wang@arm.com> wrote:
>
> This patch set includes changes proposed for BNXT PMD.
> These are C11 atomic and synchronization changes. Occurrences of
> rte_atomicNN and rte_smp_XX are touched.
>
> Ruifeng Wang (2):
> net/bnxt: use compiler atomics for stats
> net/bnxt: remove some dead code
ACK. Thanks
Patches applied to dpdk-next-net-brcm.
>
> drivers/net/bnxt/bnxt_cpr.h | 14 --------------
> drivers/net/bnxt/bnxt_rxq.c | 2 +-
> drivers/net/bnxt/bnxt_rxq.h | 2 +-
> drivers/net/bnxt/bnxt_rxr.c | 9 +++++----
> drivers/net/bnxt/bnxt_stats.c | 4 ++--
> 5 files changed, 9 insertions(+), 22 deletions(-)
>
> --
> 2.25.1
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4218 bytes --]
prev parent reply other threads:[~2022-05-23 0:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 6:31 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
2022-05-23 0:55 ` Ajit Khaparde [this message]
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='CACZ4nhuO-UmFKxdJbagsz8jgv=YMrnujBKzwo8qikh8X1twG=Q@mail.gmail.com' \
--to=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=nd@arm.com \
--cc=ruifeng.wang@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).