From: David Miller <davem@davemloft.net>
To: ktkhai@virtuozzo.com
Cc: socketcan@hartkopp.net, mkl@pengutronix.de,
linux-can@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: Convert can_pernet_ops
Date: Thu, 22 Mar 2018 11:14:46 -0400 (EDT) [thread overview]
Message-ID: <20180322.111446.684646225881760803.davem@davemloft.net> (raw)
In-Reply-To: <152145954531.26024.3744883546191004693.stgit@localhost.localdomain>
From: Kirill Tkhai <ktkhai@virtuozzo.com>
Date: Mon, 19 Mar 2018 14:39:05 +0300
> These pernet_operations create and destroy /proc entries
> and cancel per-net timer.
>
> Also, there are unneed iterations over empty list of net
> devices, since all net devices must be already moved
> to init_net or unregistered by default_device_ops. This
> already was mentioned here:
>
> https://marc.info/?l=linux-can&m=150169589119335&w=2
>
> So, it looks safe to make them async.
>
> Signed-off-by: Kirill Tkhai <ktkhai@virtuozzo.com>
Applied.
prev parent reply other threads:[~2018-03-22 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 11:38 [PATCH net-next can] Converting pernet_operations (part #9) Kirill Tkhai
2018-03-19 11:39 ` [PATCH net-next] net: Convert can_pernet_ops Kirill Tkhai
2018-03-22 15:14 ` David Miller [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=20180322.111446.684646225881760803.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ktkhai@virtuozzo.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
/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