From: Petr Vorel <petr.vorel@gmail.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
m.patzlaff@pilz.de, afshin.nasser@gmail.com,
angelo.compagnucci@gmail.com,
Arnout Vandecappelle <arnout@mind.be>,
Matthew Weber <matthew.weber@rockwellcollins.com>,
John Stultz <john.stultz@linaro.org>
Subject: Re: [PATCH 1/1] merge_config.sh: Replace prefix CONFIG_ with any prefix
Date: Mon, 29 Oct 2018 19:27:30 +0100 [thread overview]
Message-ID: <20181029182728.GB24489@x230> (raw)
In-Reply-To: <CAK7LNATFij3J+y=LuUvdrGonFa4gpcC8GBwNKN+Av2FOYbM_rQ@mail.gmail.com>
Hi Masahiro,
> Please send v2 with the commit log properly filled.
OK I'll do.
> I will take my credit as Suggested-by.
Sure :).
> > > +# Check the environment variable "CONFIG_" for the config option prefix.
> > > +# If unset, the default is "CONFIG_".
> > > +: ${CONFIG_=CONFIG_}
> > Although I guess this could be less cryptic:
> > CONFIG_="${CONFIG_:-CONFIG_}"
> You should not use the colon
> because we want to allow the environment variable
> 'CONFIG_' being set as empty.
How about having default 'CONFIG_' and if it's empty change it to
'[A-Z0-9_]\+' ? I know, it's different from C definition in lkc.h, but IMHO it'd
make sense. But I guess you prefer your suggestion CONFIG_PREFIX=${CONFIG_-CONFIG_}
> In fact, Buildroot uses empty prefix instead of "BR2_".
> In my understanding, Buildroot just has a convention where
> symbols in Config.in files start with "BR2_".
IMHO buildroot uses 'BR2_' prefix. That's what we want to use with
merge_config.sh.
Kind regards,
Petr
next prev parent reply other threads:[~2018-10-30 3:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-28 12:55 [PATCH 1/1] merge_config.sh: Replace prefix CONFIG_ with any prefix Petr Vorel
2018-10-29 15:22 ` Masahiro Yamada
2018-10-29 15:40 ` Petr Vorel
2018-10-29 16:22 ` Masahiro Yamada
2018-10-29 18:27 ` Petr Vorel [this message]
2018-10-29 19:18 ` Masahiro Yamada
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=20181029182728.GB24489@x230 \
--to=petr.vorel@gmail.com \
--cc=afshin.nasser@gmail.com \
--cc=angelo.compagnucci@gmail.com \
--cc=arnout@mind.be \
--cc=john.stultz@linaro.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=m.patzlaff@pilz.de \
--cc=matthew.weber@rockwellcollins.com \
--cc=yamada.masahiro@socionext.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox