From: Paul Bolle <pebolle@tiscali.nl>
To: Jan Beulich <JBeulich@suse.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
akpm@linux-foundation.org, Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH v2 1/2] kconfig: don't silently ignore unhandled characters
Date: Fri, 16 Jan 2015 18:53:46 +0100 [thread overview]
Message-ID: <1421430826.8562.42.camel@x220> (raw)
In-Reply-To: <54B94B3E0200007800055F77@mail.emea.novell.com>
On Fri, 2015-01-16 at 16:32 +0000, 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.) And I think the sound/soc/intel/Kconfig
> > should be a separate patch.
>
> 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 and just mention the effect the
> patch has. Following up with the various subsystem maintainers
> until they pick up patches is, hmm, difficult.
Certainly. Just a few days ago I sent out a reminder to some maintainers
that, at best, borders on counterproductive.
In this case Jiri might be the quickest road to trivial success. Jiri
responds in a reasonable time, hardly ever misses patches, and doesn't
bark if you dare send a reminder. Anyhow, I wish I had sent out the
trivial patch to fix that Kconfig last year. Then we wouldn't have had
this conversation.
Paul Bolle
next prev parent reply other threads:[~2015-01-16 17:53 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 [this message]
2015-01-19 10:28 ` Jiri Kosina
2015-01-19 12:50 ` Michal Marek
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=1421430826.8562.42.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=JBeulich@suse.com \
--cc=akpm@linux-foundation.org \
--cc=jkosina@suse.cz \
--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 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.