From: Paul Bolle <pebolle@tiscali.nl>
To: Jan Beulich <JBeulich@suse.com>
Cc: linux-kbuild@vger.kernel.org, akpm@linux-foundation.org,
Michal Marek <mmarek@suse.cz>
Subject: Re: [PATCH v3 0/3] kconfig: enhance parsing and operator recognition
Date: Thu, 12 Mar 2015 13:34:24 +0100 [thread overview]
Message-ID: <1426163664.5304.49.camel@x220> (raw)
In-Reply-To: <54BE5D52020000780005705C@mail.emea.novell.com>
On Tue, 2015-01-20 at 12:51 +0000, Jan Beulich wrote:
> There being at least one case (DEBUG_UART_8250_WORD in
> arch/arm/Kconfig.debug) where the utility silently behaves other than
> what the programmer expects tells us that (a) we shouldn't silently
> ignore unrecognized characters and (b) it's not just me always having
> wanted to be able to use comparisons other than (in)equality ones.
>
> 1: trivial: sound/soc/intel/Kconfig: use single backslash for line continuation
This turned out to be already fixed by commit 34084a436703 ("ASoC:
intel: Remove superfluous backslash in Kconfig"), which was added in
v4.0-rc1.
> 2: kconfig: don't silently ignore unhandled characters
> 3: kconfig: allow use of relations other than (in)equality
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
What's the status on 2: and 3:? Is everyone waiting on someone else to
do something? (One thing I remember is that Michal wanted the changes to
the _shipped files separately. Is that correct?)
For my part I still think 2: should go in.
And for 3: I would like to see related changes to Kconfig files
submitted too. But, of course, whether that is actually needed is mostly
Michal's call.
> v3: Split off sound/soc/intel/Kconfig change from patch 1 (now 2).
> v2: printf() -> fprintf(stderr, ) upon Paul Bolle's request. Replace
> two instances of double backslash line continuations with single
> ones in sound/soc/intel/Kconfig. Drop stray debugging printf()s
> from patch 2.
Paul Bolle
next prev parent reply other threads:[~2015-03-12 12:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 12:51 [PATCH v3 0/3] kconfig: enhance parsing and operator recognition Jan Beulich
2015-03-12 12:34 ` Paul Bolle [this message]
2015-03-12 12:42 ` Jan Beulich
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=1426163664.5304.49.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=JBeulich@suse.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=mmarek@suse.cz \
/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