From: Jeppe Ledet-Pedersen <jlp@gomspace.com>
To: Oliver Hartkopp <socketcan@hartkopp.net>,
Marc Kleine-Budde <mkl@pengutronix.de>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: linux-can moderated?
Date: Thu, 30 Apr 2015 19:17:00 +0200 [thread overview]
Message-ID: <5542638C.80806@gomspace.com> (raw)
In-Reply-To: <55422C3D.3070309@hartkopp.net>
On 30/04/15 15:21, Oliver Hartkopp wrote:
> Hi Jeppe
Hi Oliver,
> On 30.04.2015 10:28, Jeppe Ledet-Pedersen wrote:
>
>> I just sent in my first kernel patch yesterday. It successfully found
>> its way to the linux-kernel and netdev mailing lists:
>>
>> http://www.spinics.net/lists/kernel/msg1977865.html
>> http://www.spinics.net/lists/netdev/msg326785.html
>>
>> It should also have been cc'ed to linux-can@vger.kernel.org, but as far
>> as I can see, it hasn't showed up in the linux-can list archives.
>
> Yes.
>
> And it showed up there automatically:
>
> http://marc.info/?l=linux-can&m=143032208916337&w=2
Ah, thanks. I was looking at the gmane archive of linux-can (linked from
vger.kernel.org) for yesterday and couldn't find it.
http://vger.kernel.org/vger-lists.html#linux-can
http://blog.gmane.org/gmane.linux.can/day=20150429
>> I
>> believe the patch has to go in through the linux-can tree?
>
> Yes.
>
> Marc (see CC) will pick it up and commit it to the linux-can git tree at:
>
> http://git.kernel.org/cgit/linux/kernel/git/mkl/linux-can.git/
>
> where David Miller (net maintainer) will pull it from for upstream and
> stable trees.
>
> So for CAN drivers linux-can ML is perfect.
> No need for cross posting on Kernel/Netdev for CAN driver stuff.
Ok, thanks for the clarification. I thought I had to send it to all
addresses from the get_maintainer.pl script, but of course it makes more
sense only to send it to the most specific list. Sorry for the noise :)
>> Is the list moderated for non-subscribers?
>
> No.
>
>> At the time I sent the patch,
>> I wasn't subscribed to linux-can. Or did I do something else wrong?
>
> No everything went fine :-)
Great.
> Thanks for your contribution.
Thanks for explaining this - much appreciated!
-Jeppe
prev parent reply other threads:[~2015-04-30 17:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5541E79A.2050508@gomspace.com>
2015-04-30 13:21 ` linux-can moderated? Oliver Hartkopp
2015-04-30 17:17 ` Jeppe Ledet-Pedersen [this message]
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=5542638C.80806@gomspace.com \
--to=jlp@gomspace.com \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).