From: patchwork-bot+netdevbpf@kernel.org
To: Arnd Bergmann <arnd@kernel.org>
Cc: alex.aring@gmail.com, stefan@datenfreihafen.org,
miquel.raynal@bootlin.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
arnd@arndb.de, horms@kernel.org, security@auditcode.ai,
kees@kernel.org, linux-wpan@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] [net-next v3] ieee802154: avoid deprecated .ndo_do_ioctl callback
Date: Sun, 20 Sep 2026 00:10:05 +0000 [thread overview]
Message-ID: <178986300540.1499536.16990573585709011019.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260915211538.1519815-1-arnd@kernel.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 15 Sep 2026 23:14:03 +0200 you wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> The ieee802154 socket implementation is the last remaining caller of the
> netdevice ioctl callback. In order to completely remove this, add a custom
> pointer to the existing wpan_dev specific operations structure. Since that
> structure is currently only used to wrap the 'create' header operation,
> adjust the naming slightly to make this more generic.
>
> [...]
Here is the summary with links:
- [1/2,net-next,v3] ieee802154: avoid deprecated .ndo_do_ioctl callback
https://git.kernel.org/netdev/net-next/c/52fb7cca01e1
- [2/2,net-next,v3] net: remove ndo_do_ioctl handler
https://git.kernel.org/netdev/net-next/c/d98a52ae914e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-20 0:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 21:14 [PATCH 1/2] [net-next v3] ieee802154: avoid deprecated .ndo_do_ioctl callback Arnd Bergmann
2026-09-15 21:14 ` [PATCH 2/2] [net-next v3] net: remove ndo_do_ioctl handler Arnd Bergmann
2026-09-20 0:10 ` patchwork-bot+netdevbpf [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=178986300540.1499536.16990573585709011019.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alex.aring@gmail.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kees@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=security@auditcode.ai \
--cc=stefan@datenfreihafen.org \
/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.