From: David Ahern <dsahern@gmail.com>
To: Florian Westphal <fw@strlen.de>, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 3/4] net: use rtnl_register_module where needed
Date: Sun, 3 Dec 2017 19:57:33 -0700 [thread overview]
Message-ID: <6b09bb7f-c70c-a5bf-80a6-29950c05af15@gmail.com> (raw)
In-Reply-To: <519e7657-989c-7db4-6409-b41ba3bd55b9@gmail.com>
On 12/3/17 7:56 PM, David Ahern wrote:
> On 12/2/17 1:44 PM, Florian Westphal wrote:
>> all of these can be compiled as a module, so use new
>> _module version to make sure module can no longer be removed
>> while callback/dump is in use.
>>
>> Signed-off-by: Florian Westphal <fw@strlen.de>
>> ---
>> net/bridge/br_mdb.c | 6 +++---
>> net/can/gw.c | 14 ++++++++++----
>> net/decnet/dn_dev.c | 9 ++++++---
>> net/decnet/dn_fib.c | 6 ++++--
>> net/decnet/dn_route.c | 8 ++++----
>> net/mpls/af_mpls.c | 15 +++++++++------
>> net/phonet/pn_netlink.c | 21 +++++++++++++--------
>> net/qrtr/qrtr.c | 8 ++++++--
>> 8 files changed, 55 insertions(+), 32 deletions(-)
>
> ipv6 is missing from the list. Is the thought that IPv6 can be compiled
> as a module but can't be removed?
>
nm. ipv6 is converted to use _module in patch 4.
next prev parent reply other threads:[~2017-12-04 2:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-02 20:44 [PATCH next-next 0/4] rtnetlink: rework handler (un)registering Florian Westphal
2017-12-02 20:44 ` [PATCH net-next 1/4] net: rtnetlink: use rcu to free rtnl message handlers Florian Westphal
2017-12-02 20:44 ` [PATCH net-next 2/4] rtnetlink: get reference on module before invoking handlers Florian Westphal
2017-12-02 20:44 ` [PATCH net-next 3/4] net: use rtnl_register_module where needed Florian Westphal
2017-12-04 2:56 ` David Ahern
2017-12-04 2:57 ` David Ahern [this message]
2017-12-02 20:44 ` [PATCH net-next 4/4] rtnetlink: remove __rtnl_register Florian Westphal
2017-12-04 16:34 ` [PATCH next-next 0/4] rtnetlink: rework handler (un)registering David Miller
2017-12-04 16:53 ` Florian Westphal
2017-12-04 16:57 ` 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=6b09bb7f-c70c-a5bf-80a6-29950c05af15@gmail.com \
--to=dsahern@gmail.com \
--cc=fw@strlen.de \
--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).