From: Michael Ellerman <michael@ellerman.id.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
sparclinux <sparclinux@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: kisskb: sparc-allmodconfig is actually sparc64
Date: Sat, 27 Jul 2013 23:38:27 +1000 [thread overview]
Message-ID: <1374932307.7730.3.camel@concordia> (raw)
In-Reply-To: <CAMuHMdUjaGRnHZpxs1j4VkYgTUXQNXvqu8LstpxLe8tYdf1oVw@mail.gmail.com>
On Fri, 2013-07-26 at 12:23 +0200, Geert Uytterhoeven wrote:
> Hi Michael, Stephen,
>
> The sparc-allmodconfig builds on http://kisskb.ellerman.id.au/kisskb/matrix/
> seem to be sparc64, not sparc32, allmodconfig builds.
> The sparc-allnoconfig builds are sparc32.
Ah right, we seem to have sparc and sparc64 builds, but there is only
arch/sparc now.
We'll have to sort that out next week.
> BTW, what's the simplest way to make an all*config build with fixed sparc32 or
> sparc64?
I think you can do it with KCONFIG_ALLCONFIG.
cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <michael@ellerman.id.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
sparclinux <sparclinux@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: kisskb: sparc-allmodconfig is actually sparc64
Date: Sat, 27 Jul 2013 13:38:27 +0000 [thread overview]
Message-ID: <1374932307.7730.3.camel@concordia> (raw)
In-Reply-To: <CAMuHMdUjaGRnHZpxs1j4VkYgTUXQNXvqu8LstpxLe8tYdf1oVw@mail.gmail.com>
On Fri, 2013-07-26 at 12:23 +0200, Geert Uytterhoeven wrote:
> Hi Michael, Stephen,
>
> The sparc-allmodconfig builds on http://kisskb.ellerman.id.au/kisskb/matrix/
> seem to be sparc64, not sparc32, allmodconfig builds.
> The sparc-allnoconfig builds are sparc32.
Ah right, we seem to have sparc and sparc64 builds, but there is only
arch/sparc now.
We'll have to sort that out next week.
> BTW, what's the simplest way to make an all*config build with fixed sparc32 or
> sparc64?
I think you can do it with KCONFIG_ALLCONFIG.
cheers
next prev parent reply other threads:[~2013-07-27 13:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 10:23 kisskb: sparc-allmodconfig is actually sparc64 Geert Uytterhoeven
2013-07-26 10:23 ` Geert Uytterhoeven
2013-07-27 13:38 ` Michael Ellerman [this message]
2013-07-27 13:38 ` Michael Ellerman
2013-07-30 2:04 ` Michael Ellerman
2013-07-30 2:04 ` Michael Ellerman
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=1374932307.7730.3.camel@concordia \
--to=michael@ellerman.id.au \
--cc=geert@linux-m68k.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=sparclinux@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.