From: patchwork-bot+netdevbpf@kernel.org
To: Nicolai Buchwitz <nb@tipi-net.de>
Cc: davem@davemloft.net, edumazet@kernel.org, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, kuniyu@google.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 1/3] net: move the netdev_ops checks into a helper
Date: Tue, 06 Oct 2026 00:10:25 +0000 [thread overview]
Message-ID: <179124542529.1947351.12475654404297764079.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261002094211.2350702-2-nb@tipi-net.de>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 2 Oct 2026 11:42:07 +0200 you wrote:
> register_netdevice() already does two ops sanity checks and is about to
> get a third. Collect them in netdev_check_ops().
>
> The call stays after ndo_init() because drivers set features from there.
>
> Signed-off-by: Nicolai Buchwitz <nb@tipi-net.de>
>
> [...]
Here is the summary with links:
- [net-next,v2,1/3] net: move the netdev_ops checks into a helper
https://git.kernel.org/netdev/net-next/c/57f66330c6bb
- [net-next,v2,2/3] net: reject ops-locked drivers without ndo_set_rx_mode_async
https://git.kernel.org/netdev/net-next/c/05fe748456ea
- [net-next,v2,3/3] net: reject a netdev that implements only one hwtstamp NDO
https://git.kernel.org/netdev/net-next/c/810a662abcd5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-10-06 0:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261002094211.2350702-1-nb@tipi-net.de>
2026-10-02 9:42 ` [PATCH net-next v2 1/3] net: move the netdev_ops checks into a helper Nicolai Buchwitz
2026-10-06 0:10 ` patchwork-bot+netdevbpf [this message]
2026-10-02 9:42 ` [PATCH net-next v2 2/3] net: reject ops-locked drivers without ndo_set_rx_mode_async Nicolai Buchwitz
2026-10-02 9:42 ` [PATCH net-next v2 3/3] net: reject a netdev that implements only one hwtstamp NDO Nicolai Buchwitz
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=179124542529.1947351.12475654404297764079.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nb@tipi-net.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.