netdev - Re: [PATCH] net: correct a comment for the final #endif

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 28 May 2009 08:39:35 +0200
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	jpirko@...hat.com
CC:	David Miller <davem@...emloft.net>, netdev@...r.kernel.org
Subject: Re: [PATCH] net: correct a comment for the final #endif

David Miller a écrit :
> From: Jiri Pirko <jpirko@...hat.com>
> Date: Thu, 28 May 2009 07:47:13 +0200
> 
>> Btw how do you choose what patch to apply to what tree?
> 
> It depends upon where we are in the development cycle and the
> nature of your patch.
> 
> Right now we're only applying the most critical bug fixes
> to net-2.6, anything else goes to net-next-2.6
> 

I append here some extra stuff

net-2.6 is the tree for pending patches for Linus, for the about to be
released version (2.6.30 as today)

As the merge window (for 2.6.30) is now closed, only bug fixes are allowed.

For cleanups, and new network stuff (possibly introducing new bugs),
net-next-2.6 is the right tree. This gives time for various testers
to discover bugs so we can fix them before hitting public release.

When Linus releases 2.6.30, opening merge window of one week, then all patches
pending in net-next-2.6 will take their way to Linus tree for 2.6.31

Some exceptions are allowed, but this is the general idea.

Hope this helps

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