From: Oliver Hartkopp <socketcan@hartkopp•net>
To: Linux Netdev List <netdev@vger•kernel.org>
Cc: "linux-can@vger•kernel.org" <linux-can@vger•kernel.org>,
Oliver Hartkopp <oliver.hartkopp@volkswagen•de>,
Urs Thuermann <urs.thuermann@volkswagen•de>,
Wolfgang Grandegger <wg@grandegger•com>,
Marc Kleine-Budde <mkl@pengutronix•de>
Subject: [PATCH] CAN MAINTAINERS update
Date: Tue, 03 Jan 2012 19:40:28 +0100 [thread overview]
Message-ID: <4F034B9C.2030106@hartkopp.net> (raw)
Update the CAN MAINTAINERS section:
- point out active maintainers
- pull the CAN driver discussion away from netdev ML
- point to the new CAN web site on gitorious.org
- add CAN development git repository URL to submit patches
Signed-off-by: Oliver Hartkopp <socketcan@hartkopp•net>
CC: Oliver Hartkopp <oliver.hartkopp@volkswagen•de>
CC: Urs Thuermann <urs.thuermann@volkswagen•de>
CC: Wolfgang Grandegger <wg@grandegger•com>
CC: Marc Kleine-Budde <mkl@pengutronix•de>
CC: linux-can@vger•kernel.org
---
Hello Dave,
this is the updated MAINTAINERS section for the CAN subsystem.
As Marc Kleine-Budde will send upcoming git pull requests we discussed, if we
would need an additional section like this ...
NETWORKING [CAN]
M: Marc Kleine-Budde <mkl@pengutronix•de>
L: linux-can@vger•kernel.org
W: http://gitorious.org/linux-can
T: git://gitorious.org/linux-can/linux-can-next.git
S: Maintained
F: net/can/
F: drivers/net/can/
F: include/linux/can*
to make sure for you, who's sending the pull requests ...
Is this really needed or is it ok for you like it is below?
Regards,
Oliver
diff --git a/MAINTAINERS b/MAINTAINERS
index dbf3d94..59ce369 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1698,11 +1698,9 @@ F: arch/x86/include/asm/tce.h
CAN NETWORK LAYER
M: Oliver Hartkopp <socketcan@hartkopp•net>
-M: Oliver Hartkopp <oliver.hartkopp@volkswagen•de>
-M: Urs Thuermann <urs.thuermann@volkswagen•de>
L: linux-can@vger•kernel.org
-L: netdev@vger•kernel.org
-W: http://developer.berlios.de/projects/socketcan/
+W: http://gitorious.org/linux-can
+T: git://gitorious.org/linux-can/linux-can-next.git
S: Maintained
F: net/can/
F: include/linux/can.h
@@ -1713,9 +1711,10 @@ F: include/linux/can/gw.h
CAN NETWORK DRIVERS
M: Wolfgang Grandegger <wg@grandegger•com>
+M: Marc Kleine-Budde <mkl@pengutronix•de>
L: linux-can@vger•kernel.org
-L: netdev@vger•kernel.org
-W: http://developer.berlios.de/projects/socketcan/
+W: http://gitorious.org/linux-can
+T: git://gitorious.org/linux-can/linux-can-next.git
S: Maintained
F: drivers/net/can/
F: include/linux/can/dev.h
next reply other threads:[~2012-01-03 18:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 18:40 Oliver Hartkopp [this message]
2012-01-03 18:55 ` [PATCH] CAN MAINTAINERS update David Miller
2012-01-03 19:26 ` Joe Perches
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=4F034B9C.2030106@hartkopp.net \
--to=socketcan@hartkopp$(echo .)net \
--cc=linux-can@vger$(echo .)kernel.org \
--cc=mkl@pengutronix$(echo .)de \
--cc=netdev@vger$(echo .)kernel.org \
--cc=oliver.hartkopp@volkswagen$(echo .)de \
--cc=urs.thuermann@volkswagen$(echo .)de \
--cc=wg@grandegger$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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