From: Randy Dunlap <randy.dunlap@oracle.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH] x86, mrst: The shutdown for MRST requires the SCU IPC mechanism
Date: Mon, 15 Nov 2010 10:14:06 -0800 [thread overview]
Message-ID: <20101115101406.77e072ef.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20101115173110.6877.83958.stgit@localhost.localdomain>
On Mon, 15 Nov 2010 17:31:19 +0000 Alan Cox wrote:
> From: Alan Cox <alan@linux.intel.com>
>
> Fix the build failure reported by Randy Dunlap
>
> Signed-off-by: Alan Cox <alan@linux.intel.com>
> ---
>
> arch/x86/Kconfig | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
>
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index 9e71608..afe50ec 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -387,6 +387,7 @@ config X86_MRST
> select APB_TIMER
> select I2C
> select SPI
> + select INTEL_SCU_IPC
> ---help---
> Moorestown is Intel's Low Power Intel Architecture (LPIA) based Moblin
> Internet Device(MID) platform. Moorestown consists of two chips:
Hi,
Additionally using this line from my patch:
+ select X86_PLATFORM_DEVICES
will avoid this warning (with your patch applied):
warning: (X86_MRST && PCI && PCI_GOANY && X86_32 && X86_EXTENDED_PLATFORM && X86_IO_APIC) selects INTEL_SCU_IPC which has unmet direct dependencies
(X86 && X86_PLATFORM_DEVICES && X86_MRST)
which is due to the hierarchical menu structure.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-11-15 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 17:31 Alan Cox
2010-11-15 18:14 ` Randy Dunlap [this message]
2010-11-17 12:42 ` [tip:x86/platform] x86, mrst: Fix dependencies of "select INTEL_SCU_IPC" tip-bot for Randy Dunlap
2010-11-17 12:30 ` [tip:x86/platform] x86, mrst: The shutdown for MRST requires the SCU IPC mechanism tip-bot for Alan Cox
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=20101115101406.77e072ef.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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
Powered by JetHome