From: Ben Hutchings <bhutchings@solarflare.com>
To: Zhouyi Zhou <zhouzhouyi@gmail.com>
Cc: <netdev@vger.kernel.org>
Subject: Re: question about creating patch
Date: Wed, 13 Mar 2013 17:16:45 +0000 [thread overview]
Message-ID: <1363195005.2683.8.camel@bwh-desktop.uk.solarflarecom.com> (raw)
In-Reply-To: <CAABZP2zDU9UGRARWFBP86W28=pKa2T2mo1E8CaLAaRAu7yNSuQ@mail.gmail.com>
On Thu, 2013-03-14 at 00:11 +0800, Zhouyi Zhou wrote:
> Dear Colleagues,
> I have read Kushal Koolwal's article
> "HOWTO: Create and submit your first Linux kernel patch using GIT"
> and one question remain
> which tree is preferable in git://git.kernel.org/pub/scm/ should I
> clone in git clone step,
> linux/kernel/git/stable/linux-stable.git
> or
> linux/kernel/git/davem/net.git
> Many thanks
There is an easy way to answer your question for most areas of the
kernel, which is to look for a 'T:' line in the MAINTAINERS section.
For networking you will see:
T: git git://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git
T: git git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git
The first of these is for changes that should go into the pending
release (at present that would be 3.9), limited to important bug fixes
and (sometimes) new drivers. The second is for new features and more
minor bug fixes that can wait for the next release.
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
prev parent reply other threads:[~2013-03-13 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 16:11 question about creating patch Zhouyi Zhou
2013-03-13 17:16 ` Ben Hutchings [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=1363195005.2683.8.camel@bwh-desktop.uk.solarflarecom.com \
--to=bhutchings@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=zhouzhouyi@gmail.com \
/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