| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <1363195005.2683.8.camel@bwh-desktop.uk.solarflarecom.com> Date: Wed, 13 Mar 2013 17:16:45 +0000 From: Ben Hutchings <bhutchings@...arflare.com> To: Zhouyi Zhou <zhouzhouyi@...il.com> CC: <netdev@...r.kernel.org> Subject: Re: question about creating patch 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. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists