From: Ratheesh Kannoth <rkannoth@marvell.com>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Sunil Goutham <sgoutham@marvell.com>,
Geetha sowjanya <gakula@marvell.com>,
"Subbaraya Sundeep" <sbhatta@marvell.com>,
<linux-can@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH net-next] net: use assign_bit() where applicable
Date: Fri, 18 Sep 2026 07:40:31 +0530 [thread overview]
Message-ID: <aqydl2Gao3KFhDSf@rkannoth-OptiPlex-7090> (raw)
In-Reply-To: <20260917-net-assign-bit-v1-1-e9c97965e080@nxp.com>
On 2026-09-17 at 18:09:52, Peng Fan (OSS) (peng.fan@oss.nxp.com) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> Convert open-coded if/else with set_bit/clear_bit and their
> non-atomic __set_bit/__clear_bit variants to the assign_bit/__assign_bit
> API.
>
drivers/net/ethernet/marvell/octeontx2/af/cgx.c | 10 ++-------
.../net/ethernet/marvell/octeontx2/af/cn20k/npc.c | 5 +----
.../net/ethernet/marvell/octeontx2/af/rvu_nix.c | 15 +++----------
.../net/ethernet/marvell/octeontx2/af/rvu_npa.c | 10 ++-------
For above files
Reviewed-by: Ratheesh Kannoth <rkannoth@marvell.com>
next prev parent reply other threads:[~2026-09-18 2:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 12:39 [PATCH net-next] net: use assign_bit() where applicable Peng Fan (OSS)
2026-09-17 12:46 ` sashiko-bot
2026-09-18 2:10 ` Ratheesh Kannoth [this message]
2026-09-20 0:40 ` patchwork-bot+netdevbpf
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=aqydl2Gao3KFhDSf@rkannoth-OptiPlex-7090 \
--to=rkannoth@marvell.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.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