linux-kernel - Re: PM: Summary of changes for v3.6

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 for Android: free password hash cracker in your pocket

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

Date:	Tue, 17 Jul 2012 13:53:52 -0700
From:	Colin Cross <ccross@...roid.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Kevin Hilman <khilman@...com>,
	Daniel Lezcano <daniel.lezcano@...aro.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Linux PM list <linux-pm@...r.kernel.org>,
	Len Brown <lenb@...nel.org>,
	ACPI Devel Mailing List <linux-acpi@...r.kernel.org>,
	Alan Stern <stern@...land.harvard.edu>
Subject: Re: PM: Summary of changes for v3.6

On Tue, Jul 17, 2012 at 1:52 PM, Rafael J. Wysocki <rjw@...k.pl> wrote:
> Hi,
>
> On Tuesday, July 17, 2012, Kevin Hilman wrote:
>> Rafael, Daniel,
>>
>> "Rafael J. Wysocki" <rjw@...k.pl> writes:
>>
>> > Hi all,
>> >
>> > All of the changes I'd like to include into the first PM pull request during
>> > the v3.6 merge window, except maybe for one or two patches I know are in the
>> > works, is on the 'linux-next' branch of the linux-pm.git tree now.  The summary
>> > of those changes is appended.  If anyone finds any of them objectionable,
>> > please let me know ASAP.  Also please let me know if you have any power
>> > management patches you'd like me to take for v3.6.
>> >
>>
>> Could someone please clarify the status of the coupled CPUidle series?
>>
>> There's a version of these in Daniels cpuidle-next branch and there's a
>> version of these in Len's next branch (included in linux-next), but I'm
>> still not entirely sure which branch is going upstream and which branch
>> has the latest version (but I think Daniel's is the latest)
>
> Colin says that the commits in the Len's tree match his latest version,
> so I think those commits should be merged, since they have been present
> in that tree since the 3.5 merge window.

The disappeared from Len's tree for a little while after the 3.5 merge
window, which is why they started appearing other places.  Now that
they have returned to Len's tree, hopefully to stay, they should be
considered the official version.
--
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/