public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: akpm@linux-foundation.org, Michal Marek <mmarek@suse.cz>,
	linux-kbuild@vger.kernel.org
Subject: Re: [PATCH v3 0/3] kconfig: enhance parsing and operator recognition
Date: Thu, 12 Mar 2015 12:42:19 +0000	[thread overview]
Message-ID: <550197BB020000780006900F@mail.emea.novell.com> (raw)
In-Reply-To: <1426163664.5304.49.camel@x220>

>>> On 12.03.15 at 13:34, <pebolle@tiscali.nl> wrote:
> On Tue, 2015-01-20 at 12:51 +0000, Jan Beulich wrote:
>> 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?)

Since I don't recall any requests for changes mandatory for any
of this to be accepted, I didn't plan on re-submitting unless other
changes would require the patches to be refreshed in non-trivial
ways.

> 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.

Not sure what related changes to refer to. As it stands, there is
at least one use already in the tree that this change fixes, so I
didn't think there was an immediate further need for actual uses
thereof. And of course I'm hesitant to invest work in using these
new capabilities elsewhere when I can't be certain the base
changes are going to be accepted.

Jan


      reply	other threads:[~2015-03-12 12:42 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
2015-03-12 12:42   ` Jan Beulich [this message]

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=550197BB020000780006900F@mail.emea.novell.com \
    --to=jbeulich@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=pebolle@tiscali.nl \
    /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