All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Jan Beulich <JBeulich@suse.com>, Paul Bolle <pebolle@tiscali.nl>
Cc: akpm@linux-foundation.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH v2 1/2] kconfig: don't silently ignore unhandled characters
Date: Mon, 19 Jan 2015 13:50:39 +0100	[thread overview]
Message-ID: <54BCFD9F.3080906@suse.cz> (raw)
In-Reply-To: <54B94B3E0200007800055F77@mail.emea.novell.com>

On 2015-01-16 17:32, Jan Beulich wrote:
>>>> On 16.01.15 at 17:25, <pebolle@tiscali.nl> wrote:
>> On Fri, 2015-01-16 at 15:44 +0000, Jan Beulich wrote:
>>>  scripts/kconfig/zconf.l             |    7 +
>>>  scripts/kconfig/zconf.lex.c_shipped |  195 +++++++++++++++++++-----------------
>>>  sound/soc/intel/Kconfig             |    4 
>>
>> I guess Michal would like to split the c_shipped changes in this patch
>> too. (I personally don't care.)

The change to zconf.l is rather simple (and .l sorts before .lex :)), so
it's not a big issue here.


>> And I think the sound/soc/intel/Kconfig
>> should be a separate patch. 

Yes, that would be nice.


> I simply didn't want the patch to create fallout (even if it's just
> warnings). If doing this here is deemed inappropriate, I'd likely
> drop the adjustment altogether

Since it is a trivial cleanup, you can submit it as as another patch in
this series.

Michal

      parent reply	other threads:[~2015-01-19 12:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-16 15:44 [PATCH v2 1/2] kconfig: don't silently ignore unhandled characters Jan Beulich
2015-01-16 16:25 ` Paul Bolle
2015-01-16 16:32   ` Jan Beulich
2015-01-16 17:53     ` Paul Bolle
2015-01-19 10:28       ` Jiri Kosina
2015-01-19 12:50     ` Michal Marek [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=54BCFD9F.3080906@suse.cz \
    --to=mmarek@suse.cz \
    --cc=JBeulich@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kbuild@vger.kernel.org \
    --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 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.