From: "Ken'ichi Ohmichi" <oomichi@mxs.nes.nec.co.jp>
To: Bernhard Walle <bwalle@suse.de>
Cc: kexec@lists.infradead.org
Subject: Re: [PATCH] makedumpfile: Claim to support 2.6.27
Date: Fri, 14 Nov 2008 17:43:46 +0900 [thread overview]
Message-ID: <491D3A42.5050709@mxs.nes.nec.co.jp> (raw)
In-Reply-To: <20081114093938.5cfcb2bf@hale.suse.de>
[-- Attachment #1: Type: text/plain, Size: 852 bytes --]
Bernhard Walle wrote:
> Hi Ken'ichi,
>
> * Ken'ichi Ohmichi [2008-11-14 11:09]:
>> Bernhard Walle wrote:
>>> * Ken'ichi Ohmichi [2008-11-13 18:07]:
>>>> Bernhard Walle wrote:
>>>>> According to the changelog and my tests, 2.6.27 kernel is supported. Express
>>>>> that in the LATEST_VERSION check.
>>>> Thank your for your tests and your patch.
>>>> I also tested makedumpfile on linux-2.6.27 of both i386 and x86_64,
>>>> but I have not tested on ia64 yet.
>>>> So I want to know the CPU architecture of your machine to fill the
>>>> supporting table of makedumpfile's "README" file.
>>> I tested on ia64 in that case.
>> Is your ia64 kernel discontigmem, or sparsemem ?
>
> CONFIG_DISCONTIGMEM_MANUAL=y
> CONFIG_DISCONTIGMEM=y
Thank you.
I will test on ia64 sparsemem kernel and merge your patch into the next release.
Thanks
Ken'ichi Ohmichi
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2008-11-14 8:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 9:42 [PATCH] makedumpfile: Claim to support 2.6.27 Bernhard Walle
2008-11-13 9:07 ` Ken'ichi Ohmichi
2008-11-13 11:15 ` Bernhard Walle
2008-11-14 2:09 ` Ken'ichi Ohmichi
2008-11-14 8:39 ` Bernhard Walle
2008-11-14 8:43 ` Ken'ichi Ohmichi [this message]
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=491D3A42.5050709@mxs.nes.nec.co.jp \
--to=oomichi@mxs.nes.nec.co.jp \
--cc=bwalle@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.