All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robin Holt <holt@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Patch 2/2] update generic_defconfig to support sn2.
Date: Mon, 04 Aug 2008 20:08:15 +0000	[thread overview]
Message-ID: <20080804200814.GH7290@sgi.com> (raw)
In-Reply-To: <20080802183527.GA7290@sgi.com>

On Mon, Aug 04, 2008 at 12:27:25PM -0700, Luck, Tony wrote:
> I've locally applied these config updates, but I ran into
> a regression while running my usual set of test builds.
> 
> I build a few uniprocessor configs (by taking files from
> arch/ia64/configs/ and turning off CONFIG_SMP).  The
> resulting uniprocessor generic_defconfig fails to
> build with:
> 
> drivers/misc/sgi-gru/grutables.h:308: error: field `ms_notifier' has incomplete type
> 
> I tried this:
> diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
> index 82af385..6e2dcd8 100644
> --- a/drivers/misc/Kconfig
> +++ b/drivers/misc/Kconfig
> @@ -430,7 +430,7 @@ config SGI_XP
>         depends on IA64_GENERIC || IA64_SGI_SN2 || IA64_SGI_UV || (X86_64 && SMP)
>         select IA64_UNCACHED_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
>         select GENERIC_ALLOCATOR if IA64_GENERIC || IA64_SGI_SN2
> -       select SGI_GRU if IA64_GENERIC || IA64_SGI_UV || (X86_64 && SMP)
> +       select SGI_GRU if (IA64_GENERIC || IA64_SGI_UV || X86_64) && SMP

Wouldn't this allow a !SMP build to not select GRU?  That is not
correct.  I think this is more a depends on thing, but Dean/Jack are
more appropriate for that question.

Robin

  parent reply	other threads:[~2008-08-04 20:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-02 18:35 [Patch 2/2] update generic_defconfig to support sn2 Robin Holt
2008-08-04 19:27 ` Luck, Tony
2008-08-04 20:08 ` Robin Holt [this message]
2008-08-04 20:21 ` Robin Holt
2008-08-04 20:34 ` Luck, Tony

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=20080804200814.GH7290@sgi.com \
    --to=holt@sgi.com \
    --cc=linux-ia64@vger.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.