linux-kernel - Re: [stable] Linux 2.6.32.27+drm33.12

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

Message-ID: <20101210174410.GA11952@kroah.com>
Date:	Fri, 10 Dec 2010 09:44:10 -0800
From:	Greg KH <greg@...ah.com>
To:	Stefan Bader <stefan.bader@...onical.com>
Cc:	linux-kernel@...r.kernel.org, stable@...nel.org,
	kernel-team@...ts.ubuntu.com
Subject: Re: [stable]  Linux 2.6.32.27+drm33.12

On Fri, Dec 10, 2010 at 03:33:58PM +0100, Stefan Bader wrote:
> I am announcing the release of the 2.6.32.27+drm33.12 stable tree.

I'm sorry, but that combination is anything but "stable".

> This tree is based on 2.6.32 and generally has all of the stable updates
> applied. Except those to the DRM subsystem, which was based on 2.6.33 and
> took updates from that upstream stable as long as that existed. It will
> continue to add patches to the DRM subsystem as long as they are valid
> according to the stable update rules (Documentation/stable_kernel_rules.txt).

You didn't follow that rule for the drm tree, so please, don't call this
a "stable" tree at all.

Also note the new name for longterm kernel releases, "longterm", not
"stable".

> DRM patches for this tree should be sent to kernel-team@...ts.ubuntu.com.

Why make developers do extra work for this old kernel tree?  That's not
very nice.

> This release contains patches from upstream 2.6.32.27, but dropped any patches
> to the DRM subsystem.

That doesn't seem wise, but hey, good luck with it, that's a
frankenkernel if I've ever seen one...

greg k-h
--
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/