linux-kernel - Re: [PATCH 1/2] OLPC: Only enable PCI configuration type override on XO-1

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: <4C9CF6A4.5020602@zytor.com>
Date:	Fri, 24 Sep 2010 12:06:12 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
CC:	Daniel Drake <dsd@...top.org>, tglx@...utronix.de,
	mingo@...hat.com, x86@...nel.org, linux-pci@...r.kernel.org,
	linux-kernel@...r.kernel.org, dilinger@...ued.net
Subject: Re: [PATCH 1/2] OLPC: Only enable PCI configuration type override
 on XO-1

On 09/24/2010 11:03 AM, Jesse Barnes wrote:
> On Thu, 23 Sep 2010 17:28:04 +0100 (BST)
> Daniel Drake <dsd@...top.org> wrote:
> 
>> This configuration type override is for XO-1 only and must not happen
>> on XO-1.5.
>>
>> Signed-off-by: Daniel Drake <dsd@...top.org>
>> ---
>>
>> Replaces earlier patches:
>> [PATCH 1/3] OLPC: extended board revision detection
>> [PATCH 2/3] PCI: OLPC configuration cleanup
>>
>> Due to the fact that CONFIG_OLPC is associated with multiple laptop models
>> (not only the XO-1), it makes sense to keep this as a separate configuration
>> option.
>>
>> We decided against adding functions to distinguish between XO-1/XO-1.5 as
>> we don't want to encourage laptop checking in this way. There should only be
>> one or two cases where this actually matters (here is one of them).
> 
> Applied to linux-next, thanks.
> 

I already put these two patches into -tip, which should get it into
linux-next...

	-hpa

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