All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] kconfig: add a function to get the CONFIG_ prefix
Date: Fri, 19 Oct 2012 19:01:17 +0200	[thread overview]
Message-ID: <5081875D.90105@suse.cz> (raw)
In-Reply-To: <1350589816-20447-3-git-send-email-yann.morin.1998@free.fr>

On 18.10.2012 21:50, Yann E. MORIN wrote:
> -#ifndef CONFIG_
> -#define CONFIG_ "CONFIG_"
> +/* Those two defines copied from include/linux/stringify.h */
> +#define __stringify_1(x...)	#x
> +#define __stringify(x...)	__stringify_1(x)
> +static inline const char *CONFIG_prefix(void)
> +{
> +	return __stringify(CONFIG_);

This changes the semantics of the CONFIG_ macro. Previously, a
double-quoted string was accepted, now you have to define it to a token
that is turned into a string. Why don't you keep it as before and just do a

return CONFIG_;

in the function?

Michal

  reply	other threads:[~2012-10-19 17:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-18 19:50 [PATCH 0/3 v2] kconfig: get the CONFIG_ prefix from the environment Yann E. MORIN
2012-10-18 19:50 ` [PATCH 1/3] kconfig: remove CONFIG_ from string constants Yann E. MORIN
2012-10-18 19:50 ` [PATCH 2/3] kconfig: add a function to get the CONFIG_ prefix Yann E. MORIN
2012-10-19 17:01   ` Michal Marek [this message]
2012-10-19 17:59     ` Yann E. MORIN
2012-10-18 19:50 ` [PATCH 3/3] kconfig: get CONFIG_ prefix from the environment Yann E. MORIN
  -- strict thread matches above, loose matches on Subject: below --
2012-10-19 23:06 [PATCH 0/3 v3] kconfig: get the " Yann E. MORIN
2012-10-19 23:06 ` [PATCH 2/3] kconfig: add a function to get the CONFIG_ prefix Yann E. MORIN
2012-10-09 22:46 [PATH 0/3] kcofnig: get the CONFIG_ prefix from the environment Yann E. MORIN
2012-10-09 22:46 ` [PATCH 2/3] kconfig: add a function to get the CONFIG_ prefix Yann E. MORIN

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=5081875D.90105@suse.cz \
    --to=mmarek@suse.cz \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yann.morin.1998@free.fr \
    /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.