From: Sam Ravnborg <sam@ravnborg.org>
To: Bastian Blank <bastian@waldi.eu.org>,
"David S. Miller" <davem@davemloft.net>,
linux-sparc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sparc: Use 64BIT config entry
Date: Fri, 2 Jan 2009 09:04:20 +0100 [thread overview]
Message-ID: <20090102080420.GA2107@uranus.ravnborg.org> (raw)
In-Reply-To: <20090101193504.GA4368@wavehammer.waldi.eu.org>
On Thu, Jan 01, 2009 at 08:35:04PM +0100, Bastian Blank wrote:
> Use 64BIT config entry to distinguish between 32 and 64bit builds
> instead of relying on the ARCH setting. Using sparc64 as ARCH still
> forces 64BIT on.
Hi Bastian.
I have tested the patch and it works as expected.
One small nit below.
Sam
>
> Inspired by the x86 and s390 configs.
>
> Signed-off-by: Bastian Blank <waldi@debian.org>
>
> --
> You can't evaluate a man by logic alone.
> -- McCoy, "I, Mudd", stardate 4513.3
> diff --git a/arch/sparc/Kconfig b/arch/sparc/Kconfig
> index 0a94d9c..73ddfd9 100644
> --- a/arch/sparc/Kconfig
> +++ b/arch/sparc/Kconfig
> @@ -4,6 +4,13 @@
>
> mainmenu "Linux/SPARC Kernel Configuration"
>
> +config 64BIT
> + bool "64-bit kernel" if ARCH = "sparc"
> + default ARCH = "sparc64"
> + help
> + Say yes to build a 64-bit kernel - formerly known as sparc64
> + Say no to build a 32-bit kernel - formerly known as sparc
We should update this help escription with something remotely like this:
> + SPARC is a family of RISC microprocessors designed and marketed by
> + Sun Microsystems, incorporated. They are very widely found in Sun
> + workstations and clones.
Just a raw copy from the (always hidden) help text for SPARC32.
Sam
next prev parent reply other threads:[~2009-01-02 8:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-01 19:35 Bastian Blank
2009-01-02 8:04 ` Sam Ravnborg [this message]
2009-01-05 7:03 ` David Miller
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=20090102080420.GA2107@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=bastian@waldi.eu.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparc@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®