From: "Michał Mirosław" <mirqus@gmail.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH] net: spread __net_init, __net_exit
Date: Sun, 17 Jan 2010 21:15:07 +0100 [thread overview]
Message-ID: <e2d7436a1001171215m2270416fj83f40646f09507a8@mail.gmail.com> (raw)
In-Reply-To: <20100117133532.GB6178@x200>
Hello,
2010/1/17 Alexey Dobriyan <adobriyan@gmail.com>:
> __net_init/__net_exit are apparently not going away, so use them
> to full extent.
>
> In some cases __net_init was removed, because it was called from
> __net_exit code.
Maybe it's worth creating a __X_init_or_exit (or similar) for this
kind of functions? I.e. for modules it would put the code into .init
when modules are not unloadable or built in and so could be freed
after boot/module init.
Best Regards,
Michał Mirosław
next prev parent reply other threads:[~2010-01-17 20:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-17 13:35 [PATCH] net: spread __net_init, __net_exit Alexey Dobriyan
2010-01-17 20:15 ` Michał Mirosław [this message]
2010-01-18 3:16 ` David Miller
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=e2d7436a1001171215m2270416fj83f40646f09507a8@mail.gmail.com \
--to=mirqus@gmail.com \
--cc=adobriyan@gmail.com \
--cc=davem@davemloft.net \
--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).