linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@grandegger.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Oliver Hartkopp <socketcan@hartkopp.net>,
	socketcan-core@lists.berlios.de,
	"linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
	Urs Thuermann <urs@isnogud.escape.de>
Subject: Re: [RFC PATCH] CAN MAINTAINERS
Date: Fri, 02 Dec 2011 13:34:32 +0100	[thread overview]
Message-ID: <4ED8C5D8.6000505@grandegger.com> (raw)
In-Reply-To: <4ED8C2EB.1070507@pengutronix.de>

Hi Marc,

On 12/02/2011 01:22 PM, Marc Kleine-Budde wrote:
> On 12/02/2011 09:46 AM, Oliver Hartkopp wrote:
>> Hey Marc,
>>
>> i'm not as good as you using git. Indeed i'm a git newbie and do not have the
>> time right now to get in that deep that i dare to post correct pull requests
>> to netdev.
>>
>> Following the hints from Dave i checked the MAINTAINERS file how the wireless
>> guys handle their subsystem in detail. Regarding John Linville, who's
>> collecting all the stuff from several people to send finally push requests to
>> Dave i would suggest that you become our 'John Linville for CAN'.
> 
> Wolfgang and me talked about this (via PM), too. We do the job together,
> but I send the pull requests to Dave.

Thanks!

>> You speak git fluently and you know the project very good - so my suggestion
>> to clean up the MAINTAINTERS file is this:
> 
> The cleanups look got, however, do we need the linux-can tree. Do the
> wireless people have two trees?

I would drop it for the time being.

>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 717d9e9..af8a0a9 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -1707,11 +1707,8 @@ 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
> 
> this should focus the discussion on linux-can

Well, but I think the patches still need to be presented on the netdev
ml? We should clarify that.

>> -W:	http://developer.berlios.de/projects/socketcan/
>> +W:	http://gitorious.org/linux-can
> 
> the can utils are now migrated (im my repo still)
> 
>>  S:	Maintained
>>  F:	net/can/
>>  F:	include/linux/can.h
>> @@ -1723,8 +1720,7 @@ F:	include/linux/can/gw.h
>>  CAN NETWORK DRIVERS
>>  M:	Wolfgang Grandegger <wg@grandegger.com>
>>  L:	linux-can@vger.kernel.org
>> -L:	netdev@vger.kernel.org
>> -W:	http://developer.berlios.de/projects/socketcan/
>> +W:	http://gitorious.org/linux-can
>>  S:	Maintained
>>  F:	drivers/net/can/
>>  F:	include/linux/can/dev.h
>> @@ -4587,6 +4583,17 @@ F:	include/linux/wireless.h
>>  F:	include/net/iw_handler.h
>>  F:	drivers/net/wireless/
>>
>> +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.git
> 
> do we need this tree?

I don't think so. You should be added to the CAN NETWORK DRIVERS entry
above.

Wolfgang.


  reply	other threads:[~2011-12-02 12:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <48E9EDF6.4000009@pengutronix.de>
2011-11-30 22:55 ` git-tree, NOW! Marc Kleine-Budde
     [not found]   ` <4ED6B460.2010508-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-12-01  8:04     ` Wolfgang Grandegger
     [not found]       ` <4ED7351E.2010907-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2011-12-01  9:16         ` Marc Kleine-Budde
     [not found]           ` <4ED745F6.8030302-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-12-01  9:30             ` Wolfgang Grandegger
     [not found]               ` <4ED7494F.6080603-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2011-12-01  9:37                 ` Marc Kleine-Budde
2011-12-01 10:49                   ` Oliver Hartkopp
2011-12-01 11:03                     ` Marc Kleine-Budde
     [not found]                       ` <4ED75EED.6010009-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2011-12-02  8:46                         ` [RFC PATCH] CAN MAINTAINERS Oliver Hartkopp
     [not found]                           ` <4ED89050.3040201-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
2011-12-02 12:22                             ` Marc Kleine-Budde
2011-12-02 12:34                               ` Wolfgang Grandegger [this message]
2011-12-02 13:15                                 ` Oliver Hartkopp
     [not found]                                   ` <4ED8CF58.3010109-fJ+pQTUTwRTk1uMJSBkQmQ@public.gmane.org>
2011-12-02 13:34                                     ` Wolfgang Grandegger
2011-12-02 13:55                                       ` Oliver Hartkopp
     [not found]                                 ` <4ED8C5D8.6000505-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2011-12-02 14:08                                   ` 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=4ED8C5D8.6000505@grandegger.com \
    --to=wg@grandegger.com \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=socketcan-core@lists.berlios.de \
    --cc=socketcan@hartkopp.net \
    --cc=urs@isnogud.escape.de \
    /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).