From: Andrew Morton <akpm@linux-foundation.org>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Arnd Bergmann <arnd@arndb.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Maximilian Attems <max@stro.at>,
Geoff Levand <geoff@infradead.org>, Michal Marek <mmarek@suse.cz>,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] headers_check: don't warn about kexec.h
Date: Tue, 13 Jan 2015 16:47:26 -0800 [thread overview]
Message-ID: <20150113164726.72ab8dec58aabf332fd4e1a0@linux-foundation.org> (raw)
In-Reply-To: <1421183111.15397.34.camel@x220>
On Tue, 13 Jan 2015 22:05:11 +0100 Paul Bolle <pebolle@tiscali.nl> wrote:
> [Dragging Andrew, Linus, and Maximilian into this thread.]
>
> On Tue, 2015-01-13 at 21:27 +0100, Arnd Bergmann wrote:
> > On Tuesday 13 January 2015 18:13:32 Paul Bolle wrote:
> > > The last time that Geoff has been trying to get that patch applied
> > > should be
> > > http://lkml.kernel.org/r/b0702fc4186db21820d686e89afd6480560823db.1415837218.git.geoff@infradead.org>
> > > I'd rather see that go in.
> >
> > Fine with me as well. As long as we can find someone to take one of
> > the patches, I'm happy.
>
> Since Geoff's patch (and my preceding, identical patch) basically is a
> partial revert of commit 29a5c67e7a78 ("kexec: export kexec.h to user
> space") that should probably be done by either Andrew or Linus.
>
> (This short thread starts at
> http://lkml.kernel.org/r/12825174.7oxZXDxNhV@wuerfel .)
hm, sorry, I can't imagine why I didn't process Geoff's patch series
back in November. They all look good - I grabbed them.
prev parent reply other threads:[~2015-01-14 0:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 16:19 [PATCH] headers_check: don't warn about kexec.h Arnd Bergmann
2015-01-13 17:13 ` Paul Bolle
2015-01-13 20:27 ` Arnd Bergmann
2015-01-13 21:05 ` Paul Bolle
2015-01-14 0:47 ` Andrew Morton [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=20150113164726.72ab8dec58aabf332fd4e1a0@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=geoff@infradead.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=max@stro.at \
--cc=mmarek@suse.cz \
--cc=pebolle@tiscali.nl \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).