From: Dean Nelson <dcn@sgi.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Tejun Heo <tj@kernel.org>,
linux-ia64 <linux-ia64@vger.kernel.org>,
linux-next <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] SGI IA64 UV: fix ia64 build error in the linux-next tree
Date: Wed, 11 Feb 2009 19:33:19 +0000 [thread overview]
Message-ID: <20090211193319.GA21987@sgi.com> (raw)
In-Reply-To: <57C9024A16AD2D4C97DC78E552063EA361689D7D@orsmsx505.amr.corp.intel.com>
On Wed, Feb 11, 2009 at 10:58:19AM -0800, Luck, Tony wrote:
> > What question was that? Folding back across that distance is not possible
> > in a Git workflow. I do regular cross-builds - the build bug did not trigger
> > with the ia64 defconfig.
>
> I'm confused by this, as it definitely triggered for me. Perhaps
> my build scripts do things a bit differently. Essentially I do:
>
> $ for c in `ls arch/ia64/configs`
> > do
> > cp arch/ia64/configs/$i .config
> > yes '' | make oldconfig
> > make
> > done
>
> Which takes the default answer for any new questions that crop
> up. This enabled the GRU driver in the case of the generic_defconfig,
> and so the build failed because of the lack of asm/uv.h
It always triggers for me as well. I also use generic_defconfig and
request the default for any NEW questions.
WARNING: multiple messages have this Message-ID (diff)
From: Dean Nelson <dcn@sgi.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Tejun Heo <tj@kernel.org>,
linux-ia64 <linux-ia64@vger.kernel.org>,
linux-next <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] SGI IA64 UV: fix ia64 build error in the linux-next tree
Date: Wed, 11 Feb 2009 13:33:19 -0600 [thread overview]
Message-ID: <20090211193319.GA21987@sgi.com> (raw)
In-Reply-To: <57C9024A16AD2D4C97DC78E552063EA361689D7D@orsmsx505.amr.corp.intel.com>
On Wed, Feb 11, 2009 at 10:58:19AM -0800, Luck, Tony wrote:
> > What question was that? Folding back across that distance is not possible
> > in a Git workflow. I do regular cross-builds - the build bug did not trigger
> > with the ia64 defconfig.
>
> I'm confused by this, as it definitely triggered for me. Perhaps
> my build scripts do things a bit differently. Essentially I do:
>
> $ for c in `ls arch/ia64/configs`
> > do
> > cp arch/ia64/configs/$i .config
> > yes '' | make oldconfig
> > make
> > done
>
> Which takes the default answer for any new questions that crop
> up. This enabled the GRU driver in the case of the generic_defconfig,
> and so the build failed because of the lack of asm/uv.h
It always triggers for me as well. I also use generic_defconfig and
request the default for any NEW questions.
next prev parent reply other threads:[~2009-02-11 19:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 16:25 [PATCH] SGI IA64 UV: fix ia64 build error in the linux-next tree Dean Nelson
2009-02-09 16:25 ` Dean Nelson
2009-02-10 21:25 ` [PATCH] SGI IA64 UV: fix ia64 build error in the linux-next Andrew Morton
2009-02-10 21:25 ` [PATCH] SGI IA64 UV: fix ia64 build error in the linux-next tree Andrew Morton
2009-02-11 15:01 ` Dean Nelson
2009-02-11 15:01 ` Dean Nelson
2009-02-11 15:05 ` [PATCH] SGI IA64 UV: fix ia64 build error in the linux-next Ingo Molnar
2009-02-11 15:05 ` [PATCH] SGI IA64 UV: fix ia64 build error in the linux-next tree Ingo Molnar
2009-02-11 15:12 ` Dean Nelson
2009-02-11 15:12 ` Dean Nelson
2009-02-11 18:58 ` Luck, Tony
2009-02-11 18:58 ` Luck, Tony
2009-02-11 19:33 ` Dean Nelson [this message]
2009-02-11 19:33 ` Dean Nelson
2009-02-11 20:25 ` Ingo Molnar
2009-02-11 20:25 ` Ingo Molnar
2009-02-11 12:32 ` [PATCH] SGI IA64 UV: fix ia64 build error in the linux-next Ingo Molnar
2009-02-11 12:32 ` [PATCH] SGI IA64 UV: fix ia64 build error in the linux-next tree Ingo Molnar
2009-02-11 18:49 ` Luck, Tony
2009-02-11 18:49 ` 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=20090211193319.GA21987@sgi.com \
--to=dcn@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tj@kernel.org \
--cc=tony.luck@intel.com \
/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.