From: Vivek Goyal <vgoyal@redhat.com>
To: Michael Holzheu <holzheu@linux.vnet.ibm.com>
Cc: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jan Willeke <willeke@de.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-kernel@vger.kernel.org, kexec@lists.infradead.org
Subject: Re: [PATCH v7 0/5] kdump: Allow ELF header creation in new kernel
Date: Thu, 18 Jul 2013 10:38:34 -0400 [thread overview]
Message-ID: <20130718143834.GC785@redhat.com> (raw)
In-Reply-To: <20130718163121.0b7fdcba@holzheu>
On Thu, Jul 18, 2013 at 04:31:21PM +0200, Michael Holzheu wrote:
[..]
> > Hi Michael,
> >
> > Once this patch series gets merged for 3.12, can we first do some cleanup
> > of s390 code before we do further development there. Basically there is
> > no reason that s390 kdump should be any different than x86. So all the
> > logic of OLD base can go away.
>
> Hello Vivek,
>
> You mean that we first integrate the agreed "ELF header in new memory"
> patch series, then do the cleanup, and after that we discuss the further
> development (storage keys)?
Yes.
Thanks
Vivek
next prev parent reply other threads:[~2013-07-18 14:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF6010D9F0.5A45F2CF-ONC1257BAB.002B1F3E-C1257BAB.002B2812@de.ibm.com>
2013-07-17 16:00 ` [PATCH v7 0/5] kdump: Allow ELF header creation in new kernel 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 [this message]
2013-07-16 16:18 Michael Holzheu
2013-07-16 17:24 ` Vivek Goyal
2013-07-17 21:32 ` Andrew Morton
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=20130718143834.GC785@redhat.com \
--to=vgoyal@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=d.hatayama@jp.fujitsu.com \
--cc=heiko.carstens@de.ibm.com \
--cc=holzheu@linux.vnet.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.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