From: arvid.brodin@alten.se (Arvid Brodin)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to contribute to latest -rc kernel?
Date: Thu, 28 Nov 2013 18:31:19 +0100 [thread overview]
Message-ID: <52977DE7.6010105@alten.se> (raw)
In-Reply-To: <87y549j68z.fsf@nemi.mork.no>
On 2013-11-28 09:11, Bj?rn Mork wrote:
> Arvid Brodin <arvid.brodin@alten.se> writes:
>
>> I thought the subsystem -next trees was for the next release of Linux? I.e., what
>> goes into the net-next tree now will find its way into mainline at the next
>> release window, for linux-3.14-rc1?
>
> That's correct.
>
> If your series is for the networking subsystem *and* appropriate for an
> -rcX where X > 1, then it should be based on
>
> https://git.kernel.org/cgit/linux/kernel/git/davem/net.git/
>
> and you should indicate that you want it applied to "net" instead of
> "net-next". I usually do that by including "net" in the subject prefix,
> like e. g.
>
> Subject: [PATCH net] foo: fix obvious bug
>
> but there are no strict rules about how to do this AFAIK.
>
> Note that the whole series must be applicable to "net". Don't be
> tempted to mix any features in there. Split those out in a separate
> series instead and submit for "net-next". If they depend on any of the
> changes you made to "net", then explain that dependency in the
> cover-letter.
>
> And yes, a cover-letter ("PATCH 0/X") is always a good idea when posting
> more than 1 patch in a series. Davem use them as pseudo-merge commits,
> so whatever you write there is even recorded in the history. This is a
> good place to explain why the series should be applied to "net" if that
> isn't 103% obvious (sometimes you need to know a driver pretty well to
> understand why something is a bugfix and not a feature).
>
> I believe all this is explained in more detail in the
> Documentation/networking/netdev-FAQ.txt document Fan Du pointed you to.
> That's a good place to start. There are some small differences between
> networking and most other subsystems, like comment style and stable
> submissions. There's usually no problem if you miss those details in
> the beginning - you'll just have to fix it later. But reading the FAQ
> will give you a head start.
>
>
> Bj?rn
>
Thank you Bj?rn for a great answer!
Thanks also to Fan Du for pointing to the netdev-FAQ.
--
Arvid Brodin | Consultant (Linux)
ALTEN | Knarrarn?sgatan 7 | SE-164 40 Kista | Sweden
arvid.brodin at alten.se | www.alten.se/en/
________________________________
Xdin has changed its name. From 25 November 2013 we are known as Alten. Read more at www.alten.se
prev parent reply other threads:[~2013-11-28 17:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 21:17 How to contribute to latest -rc kernel? Arvid Brodin
2013-11-26 21:23 ` Aldo Iljazi
2013-11-27 1:20 ` Fan Du
2013-11-27 16:26 ` Arvid Brodin
2013-11-28 0:42 ` Fan Du
2013-11-28 8:11 ` Bjørn Mork
2013-11-28 17:31 ` Arvid Brodin [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=52977DE7.6010105@alten.se \
--to=arvid.brodin@alten.se \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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).