From: asmadeus@codewreck.org
To: Xiu Jianfeng <xiujianfeng@huawei.com>
Cc: ericvh@gmail.com, lucho@ionkov.net, linux_oss@crudebyte.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, v9fs-developer@lists.sourceforge.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] net/9p: add __init/__exit annotations to module init/exit funcs
Date: Fri, 9 Sep 2022 20:38:42 +0900 [thread overview]
Message-ID: <YxslwvLFLTdT2R9z@codewreck.org> (raw)
In-Reply-To: <20220909103546.73015-1-xiujianfeng@huawei.com>
Xiu Jianfeng wrote on Fri, Sep 09, 2022 at 06:35:46PM +0800:
> Add missing __init/__exit annotations to module init/exit funcs.
sure, queueing.
FWIW I've checked the others all seem to have it.
>
> Signed-off-by: Xiu Jianfeng <xiujianfeng@huawei.com>
> ---
> net/9p/trans_xen.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/net/9p/trans_xen.c b/net/9p/trans_xen.c
> index 41c57d40efb6..b15c64128c3e 100644
> --- a/net/9p/trans_xen.c
> +++ b/net/9p/trans_xen.c
> @@ -511,7 +511,7 @@ static struct xenbus_driver xen_9pfs_front_driver = {
> .otherend_changed = xen_9pfs_front_changed,
> };
>
> -static int p9_trans_xen_init(void)
> +static int __init p9_trans_xen_init(void)
> {
> int rc;
>
> @@ -530,7 +530,7 @@ static int p9_trans_xen_init(void)
> module_init(p9_trans_xen_init);
> MODULE_ALIAS_9P("xen");
>
> -static void p9_trans_xen_exit(void)
> +static void __exit p9_trans_xen_exit(void)
> {
> v9fs_unregister_trans(&p9_xen_trans);
> return xenbus_unregister_driver(&xen_9pfs_front_driver);
prev parent reply other threads:[~2022-09-09 11:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 10:35 [PATCH -next] net/9p: add __init/__exit annotations to module init/exit funcs Xiu Jianfeng
2022-09-09 11:38 ` asmadeus [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=YxslwvLFLTdT2R9z@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ericvh@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=v9fs-developer@lists.sourceforge.net \
--cc=xiujianfeng@huawei.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 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).