From: "H. Peter Anvin" <hpa@zytor.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Daniel Drake <dsd@laptop.org>,
tglx@linutronix.de, mingo@redhat.com, x86@kernel.org,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
dilinger@queued.net
Subject: Re: [PATCH 1/2] OLPC: Only enable PCI configuration type override on XO-1
Date: Fri, 24 Sep 2010 12:06:12 -0700 [thread overview]
Message-ID: <4C9CF6A4.5020602@zytor.com> (raw)
In-Reply-To: <20100924110338.18c8fe83@jbarnes-desktop>
On 09/24/2010 11:03 AM, Jesse Barnes wrote:
> On Thu, 23 Sep 2010 17:28:04 +0100 (BST)
> Daniel Drake <dsd@laptop.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@laptop.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
prev parent reply other threads:[~2010-09-24 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 16:28 [PATCH 1/2] OLPC: Only enable PCI configuration type override on XO-1 Daniel Drake
2010-09-23 20:04 ` [tip:x86/olpc] x86, olpc: " tip-bot for Daniel Drake
2010-09-23 23:39 ` [PATCH 1/2] OLPC: " Andres Salomon
2010-09-24 18:03 ` Jesse Barnes
2010-09-24 19:06 ` H. Peter Anvin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C9CF6A4.5020602@zytor.com \
--to=hpa@zytor.com \
--cc=dilinger@queued.net \
--cc=dsd@laptop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.