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>,
Joe Perches <joe@perches.com>
Subject: [PATCH] fix CAN MAINTAINERS SCM tree type
Date: Tue, 03 Jan 2012 20:55:58 +0100 [thread overview]
Message-ID: <4F035D4E.2070108@hartkopp.net> (raw)
As pointed out by Joe Perches the SCM tree type was missing in my patch.
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
---
diff -u -r a/MAINTAINERS b/MAINTAINERS
--- a/MAINTAINERS 2012-01-03 20:48:07.160746574 +0100
+++ b/MAINTAINERS 2012-01-03 20:48:51.208745047 +0100
@@ -1700,7 +1700,7 @@
M: Oliver Hartkopp <socketcan@hartkopp.net>
L: linux-can@vger.kernel.org
W: http://gitorious.org/linux-can
-T: git://gitorious.org/linux-can/linux-can-next.git
+T: git git://gitorious.org/linux-can/linux-can-next.git
S: Maintained
F: net/can/
F: include/linux/can.h
@@ -1714,7 +1714,7 @@
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
+T: git 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 19:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 19:55 Oliver Hartkopp [this message]
2012-01-03 19:57 ` [PATCH] fix CAN MAINTAINERS SCM tree type 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=4F035D4E.2070108@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=joe@perches.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=oliver.hartkopp@volkswagen.de \
--cc=urs.thuermann@volkswagen.de \
--cc=wg@grandegger.com \
/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).