From: Jens Axboe <[email protected]>
To: Stefano Jordhani <[email protected]>, [email protected]
Cc: "Paolo Abeni" <[email protected]>,
"Alexander Viro" <[email protected]>,
"Christian Brauner" <[email protected]>,
"Jan Kara" <[email protected]>,
"David S. Miller" <[email protected]>,
"Eric Dumazet" <[email protected]>,
"Jakub Kicinski" <[email protected]>,
"Simon Horman" <[email protected]>,
"Pavel Begunkov" <[email protected]>,
"Kuniyuki Iwashima" <[email protected]>,
"Willem de Bruijn" <[email protected]>,
"Björn Töpel" <[email protected]>,
"Magnus Karlsson" <[email protected]>,
"Maciej Fijalkowski" <[email protected]>,
"Jonathan Lemon" <[email protected]>,
"Alexei Starovoitov" <[email protected]>,
"Daniel Borkmann" <[email protected]>,
"Jesper Dangaard Brouer" <[email protected]>,
"John Fastabend" <[email protected]>,
"Sebastian Andrzej Siewior" <[email protected]>,
"Lorenzo Bianconi" <[email protected]>,
"Joe Damato" <[email protected]>,
"Alexander Lobakin" <[email protected]>,
"Sridhar Samudrala" <[email protected]>,
"Xuan Zhuo" <[email protected]>,
"Mina Almasry" <[email protected]>,
"open list:FILESYSTEMS (VFS and infrastructure)"
<[email protected]>,
"open list" <[email protected]>,
"open list:IO_URING" <[email protected]>,
"open list:XDP SOCKETS (AF_XDP)" <[email protected]>
Subject: Re: [PATCH net-next] net: use napi_id_valid helper
Date: Wed, 12 Feb 2025 15:52:25 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAEEYqun=uM-VuWZJ5puHnyp7CY06fr5kOU3hYwnOG+AydhhmNA@mail.gmail.com>
On 2/12/25 2:15 PM, Stefano Jordhani wrote:
> In commit 6597e8d35851 ("netdev-genl: Elide napi_id when not present"),
> napi_id_valid function was added. Use the helper to refactor open-coded
> checks in the source.
For the io_uring side:
Reviewed-by: Jens Axboe <[email protected]>
--
Jens Axboe
prev parent reply other threads:[~2025-02-12 22:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 21:15 [PATCH net-next] net: use napi_id_valid helper Stefano Jordhani
2025-02-12 22:45 ` Joe Damato
2025-02-12 22:52 ` Jens Axboe [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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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