From: Oliver Hartkopp <socketcan@hartkopp.net>
To: linux-can@vger.kernel.org, davem@davemloft.net
Cc: Oliver Hartkopp <socketcan@hartkopp.net>,
mkl@pengutronix.de, dev@kicherer.org, netdev@vger.kernel.org
Subject: [PATCH 0/8] Fix and complete CAN namespace support
Date: Tue, 25 Apr 2017 08:19:37 +0200 [thread overview]
Message-ID: <20170425061945.28722-1-socketcan@hartkopp.net> (raw)
Hello Dave,
unfortunately the initial network namespace support by Mario Kicherer
(8e8cda6d737d) slipped into net-next without further review and Marc pushed
the code without my Acked-by. Due to the fact that this code was in net-next
now I spent some nights to fix, clean up, finalize and test the missing pieces
for the namespace support for the CAN subsystem in net/can.
As Marc is currently *VERY* unresponsive on the mailing list due to his 'real'
job I send this patch set directly to you to make sure it gets through the
current merge window. We are already in -rc8 and I would like to avoid to push
an incomplete functionality - that has to be fixed - to Linus.
This patch set is based on the latest net-next.
Thanks,
Oliver
Oliver Hartkopp (8):
can: fix memory leak in initial namespace support
can: remove obsolete pernet_operations definitions
can: remove obsolete definitions
can: complete initial namespace support
can: network namespace support for CAN_BCM protocol
can: network namespace support for CAN gateway
can: add Virtual CAN Tunnel driver (vxcan)
can: enable module auto loading for virtual CAN interfaces
drivers/net/can/Kconfig | 18 +++
drivers/net/can/Makefile | 1 +
drivers/net/can/vcan.c | 7 +-
drivers/net/can/vxcan.c | 316 +++++++++++++++++++++++++++++++++++++++++
include/linux/can/core.h | 4 +-
include/net/netns/can.h | 9 ++
include/uapi/linux/can/vxcan.h | 12 ++
net/can/af_can.c | 77 +++++-----
net/can/af_can.h | 9 --
net/can/bcm.c | 90 +++++++-----
net/can/gw.c | 72 ++++++----
net/can/proc.c | 141 +++++++++---------
12 files changed, 580 insertions(+), 176 deletions(-)
create mode 100644 drivers/net/can/vxcan.c
create mode 100644 include/uapi/linux/can/vxcan.h
--
2.11.0
next reply other threads:[~2017-04-25 6:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 6:19 Oliver Hartkopp [this message]
2017-04-25 6:19 ` [PATCH 1/8] can: fix memory leak in initial namespace support Oliver Hartkopp
2017-04-25 6:19 ` [PATCH 2/8] can: remove obsolete pernet_operations definitions Oliver Hartkopp
2017-04-25 6:19 ` [PATCH 3/8] can: remove obsolete definitions Oliver Hartkopp
2017-04-25 6:19 ` [PATCH 4/8] can: complete initial namespace support Oliver Hartkopp
2017-04-25 6:19 ` [PATCH 5/8] can: network namespace support for CAN_BCM protocol Oliver Hartkopp
2017-04-25 6:19 ` [PATCH 6/8] can: network namespace support for CAN gateway Oliver Hartkopp
2017-04-25 6:19 ` [PATCH 7/8] can: add Virtual CAN Tunnel driver (vxcan) Oliver Hartkopp
2017-04-25 6:19 ` [PATCH 8/8] can: enable module auto loading for virtual CAN interfaces Oliver Hartkopp
2017-04-25 6:48 ` [PATCH 0/8] Fix and complete CAN namespace support Marc Kleine-Budde
2017-04-25 8:43 ` Oliver Hartkopp
2017-04-25 8:45 ` Marc Kleine-Budde
2017-04-25 8:48 ` Oliver Hartkopp
2017-04-25 8:49 ` Marc Kleine-Budde
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=20170425061945.28722-1-socketcan@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=davem@davemloft.net \
--cc=dev@kicherer.org \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.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).