From: fan.du@windriver.com (Fan Du)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to contribute to latest -rc kernel?
Date: Wed, 27 Nov 2013 09:20:52 +0800 [thread overview]
Message-ID: <529548F4.50206@windriver.com> (raw)
In-Reply-To: <5293BE52.3060005@alten.se>
On 2013?11?26? 05:17, Arvid Brodin wrote:
> Hi,
>
> How would I go ahead to send a patch for the latest -rc kernel?
>
> Specifically:
>
> * What tree to diff against? (Linus'?)
> * To which list do I send the patch?
>
> Background: I've contributed a new network driver that is now in 3.13-rc1. I
> would like to fix it so that it behaves better with iproute. Strictly speaking
> this isn't a bug fix, but the driver is going to be quite useless without
> iproute support, and that won't be there until this fix is in the kernel.
Almost every subsystem has its own next git tree, since it's a networking driver
issue, please verify your fix against net-next:
https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/
And send the patch to netdev maillist:
http://vger.kernel.org/vger-lists.html#netdev
You need also CC the driver maintainer by looking at linux_source_code/MAINTAINERS,
or using ./scripts/get_maintainer.pl.
>
> --
> Arvid Brodin | Consultant (Linux)
> ALTEN | Knarrarn?sgatan 7 | SE-164 40 Kista | Sweden
> arvid.brodin at alten.se | www.alten.se/en/
> ________________________________
> Xdin is changing its name. From 25 November 2013 we will be known as Alten. Read more at www.alten.se
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
--
?????????
--fan fan
next prev parent reply other threads:[~2013-11-27 1:20 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 [this message]
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
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=529548F4.50206@windriver.com \
--to=fan.du@windriver.com \
--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).