linux-kernel - Re: [linux-pm] [git pull 2.6.36.stable] intel

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]

Message-id: <alpine.LFD.2.00.1011221318230.19247@x980>
Date:	Mon, 22 Nov 2010 13:36:31 -0500 (EST)
From:	Len Brown <lenb@...nel.org>
To:	stable@...nel.org
Cc:	linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [linux-pm] [git pull 2.6.36.stable] intel_idle patches for
 2.6.36.stable

Hi Greg,

I retract my intel_idle pull requests for .stable

The idle-release branches in...
git://git.kernel.org/pub/scm/linux/kernel/git/lenb/
	linux-idle-2.6.32.git
	linux-idle-2.6.35.git
	linux-idle-2.6.36.git

are for distros and others that want to run the latest intel_idle
driver on the specified release.  The backports in these trees
contain every upstream patch that touch the driver, including new
platform support and any dependent cosmetic patches.

So they are optimized for the maintenance task of comparing
the backport versus the upstream driver to verify the release
includes everything that is upstream.
However, as it does not exclude cosmetic or trivial patches,
the backports do not qualify for inclusion in .stable.

Sorry to bother you.

thanks,
Len Brown, Intel Open Source Technology Center
--
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/