From: Kirill Tkhai <ktkhai@virtuozzo.com>
To: davem@davemloft.net, socketcan@hartkopp.net, mkl@pengutronix.de,
linux-can@vger.kernel.org, netdev@vger.kernel.org,
ktkhai@virtuozzo.com
Subject: [PATCH net-next can] Converting pernet_operations (part #9)
Date: Mon, 19 Mar 2018 14:38:57 +0300 [thread overview]
Message-ID: <152145944801.26024.17416146842279639788.stgit@localhost.localdomain> (raw)
Hi,
this series continues to review and to convert pernet_operations
to make them possible to be executed in parallel for several
net namespaces at the same time. There is only one patch converting
can_pernet_ops.
Thanks,
Kirill
---
Kirill Tkhai (1):
net: Convert can_pernet_ops
net/can/af_can.c | 1 +
1 file changed, 1 insertion(+)
--
Signed-off-by: Kirill Tkhai <ktkhai@virtuozzo.com>
next reply other threads:[~2018-03-19 11:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 11:38 Kirill Tkhai [this message]
2018-03-19 11:39 ` [PATCH net-next] net: Convert can_pernet_ops Kirill Tkhai
2018-03-22 15:14 ` 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=152145944801.26024.17416146842279639788.stgit@localhost.localdomain \
--to=ktkhai@virtuozzo.com \
--cc=davem@davemloft.net \
--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