From: Simon Horman <horms@kernel.org>
To: Shi Hao <i.shihao.999@gmail.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2]: 3c515 : replace cleanup_module with __exit
Date: Mon, 20 Oct 2025 13:56:15 +0100 [thread overview]
Message-ID: <aPYxbwjIlyPHrTY3@horms.kernel.org> (raw)
In-Reply-To: <20251018052541.124365-1-i.shihao.999@gmail.com>
On Sat, Oct 18, 2025 at 10:55:41AM +0530, Shi Hao wrote:
> update old legacy cleanup_module from the file with __exit
> module as per kernel code practices and restore the #ifdef
> MODULE condition to allow successful compilation as a built
> -in driver.
>
> The file had an old cleanup_module still in use which could
> be updated with __exit module function although its init_module
> is indeed newer however the cleanup_module was still
> using the older version of exit.
>
> To set proper exit module function replace cleanup_module
> with __exit corkscrew_exit_module to align it to the
> kernel code consistency.
>
> Signed-off-by: Shi Hao <i.shihao.999@gmail.com>
>
> ---
>
> changes v2:
> - Restore ifdef module condition to compile as built in module
> - Adjust subject prefix from "net:ethernet" to "3c515"
Thanks for the update.
The code changes in this version look good to me.
One minor nit: the whitespace in the subject look slightly off.
There is probably no need to repost because of this.
But I would have gone for:
Subject: [PATCH net-next v2] 3c515: replace cleanup_module with __exit
But overall this looks good to me.
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2025-10-20 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-18 5:25 [PATCH net-next v2]: 3c515 : replace cleanup_module with __exit Shi Hao
2025-10-20 12:56 ` Simon Horman [this message]
2025-10-21 6:07 ` [PATCH net-next v2]: 3c515: " ShiHao
2025-10-22 1:50 ` [PATCH net-next v2]: 3c515 : " 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=aPYxbwjIlyPHrTY3@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=i.shihao.999@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).