From: Stephen Rothwell <sfr@canb.auug.org.au>
To: David Rientjes <rientjes@google.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
kexec@lists.infradead.org
Subject: Re: linux-next: Tree for Mar 20 (vmcore)
Date: Thu, 21 Mar 2013 13:20:12 +1100 [thread overview]
Message-ID: <20130321132012.e6f9a10287fb171dcd05c62d@canb.auug.org.au> (raw)
In-Reply-To: <alpine.DEB.2.02.1303201709440.23363@chino.kir.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 918 bytes --]
Hi,
On Wed, 20 Mar 2013 17:10:30 -0700 (PDT) David Rientjes <rientjes@google.com> wrote:
>
> On Wed, 20 Mar 2013, David Rientjes wrote:
>
> > I don't think that's it, linux/kexec.h already gets included indirectly.
> > The problem is that CONFIG_KEXEC isn't set so the definition in kexec.h is
> > meaningless.
> >
> > This comes from "vmcore: check NT_VMCORE_PAD as a mark indicating the end
> > of ELF note buffer" merged through the -mm tree. I've added the patch's
> > author and Andrew to the cc.
> >
> > How can this be protected by CONFIG_KEXEC?
>
> These patches were removed from -mm today so it should no longer be a
> problem.
What exactly are "these patches" so that I can remove them from my copy
of the mmotm tree (assuming that Andrew does not get a new mmotm released
in the next hour or so).
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-03-21 2:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 5:05 linux-next: Tree for Mar 20 Stephen Rothwell
2013-03-20 16:47 ` linux-next: Tree for Mar 20 (vmcore) Randy Dunlap
2013-03-20 18:56 ` David Rientjes
2013-03-20 18:58 ` Randy Dunlap
2013-03-21 0:10 ` David Rientjes
2013-03-21 2:20 ` Stephen Rothwell [this message]
2013-03-21 2:49 ` David Rientjes
2013-03-21 3:51 ` Stephen Rothwell
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=20130321132012.e6f9a10287fb171dcd05c62d@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=d.hatayama@jp.fujitsu.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rientjes@google.com \
/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
all inboxes | Powered by JetHome®