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: yann.morin.1998@free.fr, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH 1/2] kconfig: don't silently ignore unhandled characters
Date: Fri, 19 Dec 2014 16:31:09 +0000	[thread overview]
Message-ID: <549460DD0200007800051182@mail.emea.novell.com> (raw)
In-Reply-To: <1418120161.2058.97.camel@x220>

Hi Paul,

>>> On 09.12.14 at 11:16, <pebolle@tiscali.nl> wrote:
> It's been five weeks since you've sent this. I'm not aware of any other
> comments beside mine. Here's what I'd suggest to get things moving:
> 
> Resend these patches.

I guess I'll do this as soon as I got to merge my patch queue onto
3.19-rc, i.e. hopefully early next year.

> Don't bother sending to Yann, that's pointless. Do
> include lkml. Perhaps also include Michal Marek and/or Andrew Morton:
> one of them might handle these patches. Who knows...
> 
> For 1/2 feel free to add
>     Acked-by: Paul Bolle <pebolle@tiscali.nl>
> 
> _provided_ you change the printf([...]) to a fprintf(stderr, [...]).

While I can do that, this will end up being inconsistent with all other
code in zconf.l - it's all using printf(). I therefore think this would
better be another patch changing all of them info fprintf(stderr, ).

Jan


      reply	other threads:[~2014-12-19 16:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04  9:05 [PATCH 1/2] kconfig: don't silently ignore unhandled characters Jan Beulich
2014-11-04 14:06 ` Paul Bolle
2014-11-04 14:14   ` Jan Beulich
2014-11-05 10:36     ` Paul Bolle
2014-11-06 10:19       ` Jan Beulich
2014-11-06 10:28         ` Paul Bolle
2014-12-09 10:16     ` Paul Bolle
2014-12-19 16:31       ` 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=549460DD0200007800051182@mail.emea.novell.com \
    --to=jbeulich@suse.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    --cc=yann.morin.1998@free.fr \
    /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