From: Andrew Morton <akpm@linux-foundation.org>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
kexec@lists.infradead.org, Jan Willeke <willeke@de.ibm.com>,
linux-kernel@vger.kernel.org,
HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [PATCH v7 0/5] kdump: Allow ELF header creation in new kernel
Date: Wed, 17 Jul 2013 14:32:50 -0700 [thread overview]
Message-ID: <20130717143250.5de649f4a0fde9f1a52d73f6@linux-foundation.org> (raw)
In-Reply-To: <20130716172421.GA7982@redhat.com>
On Tue, 16 Jul 2013 13:24:21 -0400 Vivek Goyal <vgoyal@redhat.com> wrote:
> Michael, Hatayama, in case this series can't go in 3.11, do you have other
> ideas where a small hack fix will allow kdump to work on s390 and we
> don't have to revert the mmap() patches.
This would certainly be the preferred option at this stage.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2013-07-17 21:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 16:18 [PATCH v7 0/5] kdump: Allow ELF header creation in new kernel Michael Holzheu
2013-07-16 16:18 ` [PATCH v7 1/5] vmcore: Introduce ELF header in new memory feature Michael Holzheu
2013-07-16 16:18 ` [PATCH v7 2/5] s390/vmcore: Use " Michael Holzheu
2013-07-16 16:18 ` [PATCH v7 3/5] vmcore: Introduce remap_oldmem_pfn_range() Michael Holzheu
2013-07-16 16:18 ` [PATCH v7 4/5] s390/vmcore: Implement remap_oldmem_pfn_range for s390 Michael Holzheu
2013-07-16 16:18 ` [PATCH v7 5/5] s390/vmcore: Use vmcore for zfcpdump Michael Holzheu
2013-07-16 17:24 ` [PATCH v7 0/5] kdump: Allow ELF header creation in new kernel Vivek Goyal
2013-07-17 21:32 ` Andrew Morton [this message]
[not found] <OF6010D9F0.5A45F2CF-ONC1257BAB.002B1F3E-C1257BAB.002B2812@de.ibm.com>
2013-07-17 16:00 ` Michael Holzheu
2013-07-17 21:42 ` Vivek Goyal
2013-07-18 10:40 ` Michael Holzheu
2013-07-18 10:47 ` Martin Schwidefsky
2013-07-18 13:35 ` Vivek Goyal
2013-07-19 6:50 ` Martin Schwidefsky
2013-07-19 13:35 ` Vivek Goyal
2013-07-19 14:20 ` Martin Schwidefsky
2013-07-18 13:27 ` Vivek Goyal
2013-07-18 14:31 ` Michael Holzheu
2013-07-18 14:38 ` Vivek Goyal
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=20130717143250.5de649f4a0fde9f1a52d73f6@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=d.hatayama@jp.fujitsu.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=vgoyal@redhat.com \
--cc=willeke@de.ibm.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