All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Jeppe Ledet-Pedersen <jlp@gomspace.com>,
	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 15:21:01 +0200	[thread overview]
Message-ID: <55422C3D.3070309@hartkopp.net> (raw)
In-Reply-To: <5541E79A.2050508@gomspace.com>

Hi Jeppe

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

> 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.


> 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 :-)

Thanks for your contribution.

Best regards,
Oliver


       reply	other threads:[~2015-04-30 13:21 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 ` Oliver Hartkopp [this message]
2015-04-30 17:17   ` linux-can moderated? Jeppe Ledet-Pedersen

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=55422C3D.3070309@hartkopp.net \
    --to=socketcan@hartkopp.net \
    --cc=jlp@gomspace.com \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.