linux-kernel - stable cc's in linux -next was Re: [BUG] x86: bootmem broken on SGI UV

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-next>] [day] [month] [year] [list]

Message-ID: <AANLkTinyA=bSeSe7eavUb7fuSgM8m=QQFGqCrNtCGqKa@mail.gmail.com>
Date:	Sun, 10 Oct 2010 07:34:58 +1000
From:	Dave Airlie <airlied@...il.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>
Subject: stable cc's in linux -next was Re: [BUG] x86: bootmem broken on SGI UV

On Sun, Oct 10, 2010 at 4:39 AM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
> On Sat, Oct 9, 2010 at 11:06 AM, Yinghai Lu <yinghai@...nel.org> wrote:
>>
>> It is too late for put in 2.6.36. Linus already had -rc7, and assume he will have final .36 this week.
>
> Anything that is worth tagging for stable is worth fixing before the
> final release (probably Wednesday).

Do we track people dong this at all? I wonder how many patches in
linux-next have cc: stable in them but haven't been submitted to
Linus,

I know in some cases people want to soak test them for a bit longer
but not sure how much actual coverage next provides.

Dave.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/