All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Jan Beulich <JBeulich@suse.com>
Cc: akpm@linux-foundation.org, pebolle@tiscali.nl,
	linux-kbuild@vger.kernel.org
Subject: Re: [PATCH v3 2/3] kconfig: don't silently ignore unhandled characters
Date: Thu, 11 Jun 2015 14:58:04 +0200	[thread overview]
Message-ID: <557985DC.7000706@suse.cz> (raw)
In-Reply-To: <55799E180200007800083A99@mail.emea.novell.com>

On 2015-06-11 14:41, Jan Beulich wrote:
>>>> On 11.06.15 at 14:36, <mmarek@suse.cz> wrote:
>> On 2015-01-20 13:52, Jan Beulich wrote:
>>> At the very least we should tell people that what they wrote is not
>>> what the utility understands.
>>>
>>> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>>> Acked-by: Paul Bolle <pebolle@tiscali.nl>
>>> ---
>>> v3: Split off sound/soc/intel/Kconfig change.
>>> 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.
>>
>> Sorry, I completely missed v3 of this series. I applied this patch to
>> kbuild.git#kconfig now.
> 
> Thanks. What about patch 3 (which earlier on you said something
> like "nice" in reply, making me assume it would be taken too) then?

I still like it, but I also said it should be split into two patches.

Michal


      reply	other threads:[~2015-06-11 12:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20 12:52 [PATCH v3 2/3] kconfig: don't silently ignore unhandled characters Jan Beulich
2015-06-11 12:36 ` Michal Marek
2015-06-11 12:41   ` Jan Beulich
2015-06-11 12:58     ` 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=557985DC.7000706@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.