linux-kernel - Re: Please pull ACPI updates

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, 17 Jul 2008 08:47:07 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
CC:	"Rafael J. Wysocki" <rjw@...k.pl>, torvalds@...l.org,
	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org
Subject: Re: Please pull ACPI updates

Jesse Barnes wrote:
> On Wednesday, July 16, 2008 3:11 pm Rafael J. Wysocki wrote:
>> On Wednesday, 16 of July 2008, Andi Kleen wrote:
>>> Linus,
>>>
>>> Please pull from
>>>
>>>   git://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-acpi-merge-2.6
>>> release-2.6.27
>>>
>>> to get the initial ACPI updates for 2.6.27. We got a few more changes
>>> dependent on yet unpulled trees and some other candidate patches,
>>> but that's the bulk for the changes intended for 2.6.27. Most of that
>>> has been collected by Len Brown before he went on sabbatical. I was
>>> relatively conservative with additional changes so far.
>> Well, IMO it would be better to merge PCI first.
> 
> Yeah, they're interdependent (I pulled from Len's tree, hopefully Andi 
> preserved the changesets).  I had wanted to do a little more testing of what 
> I've got, but I haven't heard any huge complaints so far so maybe things are 
> ok.  I'll generate a pull request now.

Hmm, but if you're dependent ACPI needs to go in first anyways, doesn't it?

I don't think the ACPI tree is dependent on PCI at least. Or at least I didn't
notice any problems in this area.

-Andi

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