public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@redhat.com>
To: Michael Holzheu <holzheu@linux.vnet.ibm.com>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
	kexec@lists.infradead.org,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Jan Willeke <willeke@de.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] kdump: Introduce ELF header in new memory feature
Date: Thu, 23 May 2013 14:57:38 -0400	[thread overview]
Message-ID: <20130523185738.GM2779@redhat.com> (raw)
In-Reply-To: <20130523205241.4b9e4fde@holzheu>

On Thu, May 23, 2013 at 08:52:41PM +0200, Michael Holzheu wrote:
> Hello Vivek,
> 
> Thanks for your reply. I will integrate your feedback into the v3 patch
> set and will make the following changes:
> 
> - Get rid of ELFCORE_ADDR_NEWMEM (sorry for that:)
> - Make read_from_crash_header() only read from kernel
> - Move read_from_crash_header() to weak function
>   arch_read_from_crash_header()
> - Implement read_from_crash_header() strong function for s390
> - Set elfcorehdr_addr to address of new ELF header

Thanks Michael. Also note, that hatayama has posted a  new version (V8)
of his mmap() patches. So you can rebase your changes on top of V8.

Thanks
Vivek

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2013-05-23 18:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22 17:58 [PATCH v2 0/3] kdump: Allow ELF header creation in new kernel Michael Holzheu
2013-05-22 17:58 ` [PATCH v2 1/3] kdump: Introduce ELF header in new memory feature Michael Holzheu
2013-05-23 17:41   ` Vivek Goyal
2013-05-23 18:52     ` Michael Holzheu
2013-05-23 18:57       ` Vivek Goyal [this message]
2013-05-22 17:58 ` [PATCH v2 2/3] s390/kdump: Use arch function call for kdump Michael Holzheu
2013-05-22 17:58 ` [PATCH v2 3/3] s390/kdump: Use vmcore for zfcpdump Michael Holzheu

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=20130523185738.GM2779@redhat.com \
    --to=vgoyal@redhat.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