From: Daniel Borkmann <dborkman@redhat.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Christoph Jaeger <cj@linux.com>,
yann.morin.1998@free.fr, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH 2/3] kconfig: remove undocumented type definition alias 'boolean'
Date: Mon, 08 Dec 2014 20:16:51 +0100 [thread overview]
Message-ID: <5485F923.3090301@redhat.com> (raw)
In-Reply-To: <1418066039.2058.19.camel@x220>
On 12/08/2014 08:13 PM, Paul Bolle wrote:
> On Mon, 2014-12-08 at 19:51 +0100, Paul Bolle wrote:
>> This doesn't apply on next-20141208. What tree did you base this on?
>
> I got it to apply on next-20141208 by dropping the hunk for
> arch/cris/arch-v32/drivers/Kconfig and by making (trivial) context
> changes to the hunks for init/Kconfig and net/Kconfig.
>
> (My experience with actual maintainers is that they won't bother to do
> that. Anyhow, Kconfig is basically unmaintained. And I don't know which
> tree one should base ones Kconfig patches on.)
Well, I guess if in doubt then this could go into Andrew's tree. :)
> I'll muddle along...
>
>
> Paul Bolle
>
next prev parent reply other threads:[~2014-12-08 19:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 1:49 [PATCH 0/3] remove undocumented type definition alias Christoph Jaeger
2014-12-08 1:49 ` [PATCH 1/3] kconfig: regenerate parser Christoph Jaeger
2014-12-08 20:28 ` Paul Bolle
2014-12-08 1:49 ` [PATCH 2/3] kconfig: remove undocumented type definition alias 'boolean' Christoph Jaeger
2014-12-08 18:51 ` Paul Bolle
2014-12-08 19:13 ` Paul Bolle
2014-12-08 19:16 ` Daniel Borkmann [this message]
2014-12-08 19:41 ` Paul Bolle
2014-12-08 20:36 ` Paul Bolle
2014-12-08 21:15 ` Paul Bolle
2014-12-09 11:49 ` Daniel Borkmann
2014-12-09 23:14 ` Christoph Jaeger
2014-12-08 1:49 ` [PATCH 3/3] kconfig: rename S_BOOLEAN to S_BOOL for consistency Christoph Jaeger
2014-12-08 20:43 ` Paul Bolle
2014-12-08 20:20 ` [PATCH 0/3] remove undocumented type definition alias Paul Bolle
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=5485F923.3090301@redhat.com \
--to=dborkman@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cj@linux.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@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 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.