[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130311230731.0c610d86569d09f6e23b8e61@canb.auug.org.au>
Date: Mon, 11 Mar 2013 23:07:31 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Rusty Russell <rusty@...tcorp.com.au>
Cc: James Hogan <james.hogan@...tec.com>,
Al Viro <viro@...iv.linux.org.uk>,
Michal Marek <mmarek@...e.cz>,
Andrew Morton <akpm@...ux-foundation.org>,
Guenter Roeck <linux@...ck-us.net>,
Jean Delvare <khali@...ux-fr.org>,
linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org,
Mike Frysinger <vapier@...too.org>,
uclinux-dist-devel@...ckfin.uclinux.org, linux-next@...r.kernel.org
Subject: Re: [RFC -next] linux/linkage.h: fix symbol prefix handling
Hi Rusty,
On Mon, 11 Mar 2013 17:05:17 +1030 Rusty Russell <rusty@...tcorp.com.au> wrote:
>
> diff --git a/arch/blackfin/Kconfig b/arch/blackfin/Kconfig
> index 600494c..cd0f7c7 100644
> --- a/arch/blackfin/Kconfig
> +++ b/arch/blackfin/Kconfig
> @@ -1,6 +1,5 @@
> -config SYMBOL_PREFIX
> - string
> - default "_"
> +config SYMBOL_PREFIX_UNDERSCORE
> + def_bool y
Please, if you are going to do this, just have
config SYMBOL_PREFIX_UNDERSCORE
bool
in one Kconfig file (probably arch/Kconfig) and then select it from the
appropriate architecture Kconfig files. You could even put a help text
on it to explain why a new architecture may need to select it.
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists