From: Ingo Molnar <mingo@elte.hu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86, soc: Fix fallout from the previous changes
Date: Sat, 11 Feb 2012 15:50:03 +0100 [thread overview]
Message-ID: <20120211145003.GC497@elte.hu> (raw)
In-Reply-To: <20120209141517.26563.45774.stgit@bob.linux.org.uk>
* Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> From: Alan Cox <alan@linux.intel.com>
>
> The PCI fixups get executed based upon whether they are linked in. We need
> to avoid executing them if we boot a dual SoC/PC type kernel on a PC class
> system.
>
> Signed-off-by: Alan Cox <alan@linux.intel.com>
> ---
>
> arch/x86/pci/mrst.c | 12 +++++++++++-
> 1 files changed, 11 insertions(+), 1 deletions(-)
This would be for Jesse's PCI tree I think.
Thanks,
Ingo
prev parent reply other threads:[~2012-02-11 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 14:15 [PATCH] x86, soc: Fix fallout from the previous changes Alan Cox
2012-02-11 14:50 ` Ingo Molnar [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=20120211145003.GC497@elte.hu \
--to=mingo@elte.hu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox