From: patchwork-bot+netdevbpf@kernel.org
To: Ethan Nelson-Moore <enelsonmoore@gmail.com>
Cc: netdev@vger.kernel.org, linux-can@vger.kernel.org,
linux-wireless@vger.kernel.org, m.grzeschik@pengutronix.de,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, mkl@pengutronix.de,
mailhol@kernel.org, idosch@nvidia.com, petrm@nvidia.com,
sridhar.samudrala@intel.com, toke@toke.dk, pkshih@realtek.com,
tmuehlbacher@posteo.net, socketcan@hartkopp.net
Subject: Re: [PATCH net-next] net: remove unnecessary module_init/exit functions
Date: Tue, 03 Feb 2026 01:50:08 +0000 [thread overview]
Message-ID: <177008340837.1270041.12095382235661500510.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260131004327.18112-1-enelsonmoore@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 30 Jan 2026 16:42:56 -0800 you wrote:
> Many network drivers have unnecessary empty module_init and module_exit
> functions. Remove them (including some that just print a message). Note
> that if a module_init function exists, a module_exit function must also
> exist; otherwise, the module cannot be unloaded.
>
> Signed-off-by: Ethan Nelson-Moore <enelsonmoore@gmail.com>
>
> [...]
Here is the summary with links:
- [net-next] net: remove unnecessary module_init/exit functions
https://git.kernel.org/netdev/net-next/c/e0221553436b
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-02-03 1:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-31 0:42 [PATCH net-next] net: remove unnecessary module_init/exit functions Ethan Nelson-Moore
2026-01-31 15:11 ` Marc Kleine-Budde
2026-01-31 21:30 ` Michael Grzeschik
2026-02-01 13:47 ` Ido Schimmel
2026-02-02 0:39 ` Ping-Ke Shih
2026-02-02 9:17 ` Toke Høiland-Jørgensen
2026-02-02 20:29 ` Andrew Lunn
2026-02-02 20:33 ` Ethan Nelson-Moore
2026-02-02 21:56 ` Andrew Lunn
2026-02-03 0:56 ` Ethan Nelson-Moore
2026-02-03 1:50 ` 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=177008340837.1270041.12095382235661500510.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=enelsonmoore@gmail.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=m.grzeschik@pengutronix.de \
--cc=mailhol@kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=pkshih@realtek.com \
--cc=socketcan@hartkopp.net \
--cc=sridhar.samudrala@intel.com \
--cc=tmuehlbacher@posteo.net \
--cc=toke@toke.dk \
/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