From: "\"Zhou, Wenjian/周文剑\"" <zhouwj-fnst@cn.fujitsu.com>
To: kexec@lists.infradead.org
Subject: Re: [PATCH v3 0/3] make incomplete dumpfile analyzable
Date: Tue, 14 Oct 2014 09:23:43 +0800 [thread overview]
Message-ID: <543C7B1F.40804@cn.fujitsu.com> (raw)
In-Reply-To: <1413249439-12349-1-git-send-email-zhouwj-fnst@cn.fujitsu.com>
I will continue these patches.
Zhou Wenjian
On 10/14/2014 09:17 AM, Zhou Wenjian wrote:
> v2->v3:
> remove the part of changing PT_LOAD header
> add check_and_modify_headers()
>
> Wang Xiao (3):
> makedumpfile: make get_elf64_phdr()/get_elf32_phdr() public
> make the incomplete dumpfile generated by ENOSPC error analyzable
> implementation of dealing with kdump-compressed dumpfile with ENOSPC
> error
>
> diskdump_mod.h | 2 +
> elf_info.c | 71 ++++++++++----------
> elf_info.h | 2 +
> makedumpfile.c | 195 +++++++++++++++++++++++++++++++++++++++++++++++++++++---
> 4 files changed, 225 insertions(+), 45 deletions(-)
>
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2014-10-14 1:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 1:17 [PATCH v3 0/3] make incomplete dumpfile analyzable Zhou Wenjian
2014-10-14 1:17 ` [PATCH v3 1/3] makedumpfile: make get_elf64_phdr()/get_elf32_phdr() public Zhou Wenjian
2014-10-14 1:17 ` [PATCH v3 2/3] make the incomplete dumpfile generated by ENOSPC error analyzable Zhou Wenjian
2014-10-14 1:17 ` [PATCH v3 3/3] implementation of dealing with kdump-compressed dumpfile with ENOSPC error Zhou Wenjian
2014-10-14 1:23 ` "Zhou, Wenjian/周文剑" [this message]
2014-10-20 1:18 ` [PATCH v3 0/3] make incomplete dumpfile analyzable Atsushi Kumagai
2014-10-20 2:45 ` "Zhou, Wenjian/周文剑"
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=543C7B1F.40804@cn.fujitsu.com \
--to=zhouwj-fnst@cn.fujitsu.com \
--cc=kexec@lists.infradead.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