From: Bernhard Walle <bwalle@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
vgoyal@redhat.com
Subject: Re: [PATCH] Remove CONFIG_EXPERIMENTAL from kdump
Date: Thu, 26 Jun 2008 10:28:03 +0200 [thread overview]
Message-ID: <20080626102803.2a1a46cd@halley.suse.de> (raw)
In-Reply-To: <20080626012337.a73c91d2.akpm@linux-foundation.org>
* Andrew Morton [2008-06-26 01:23]:
> >
> > config PROC_VMCORE
> > bool "/proc/vmcore support (EXPERIMENTAL)"
> > - depends on PROC_FS && EXPERIMENTAL && CRASH_DUMP
> > + depends on PROC_FS && CRASH_DUMP
> > default y
> > help
> > Exports the dump image of crashed kernel in ELF format.
>
> What about powerpc, sh and ia64?
At least for ia64 I wouldn't consider it as experimental. Don't know
about SH and PPC. But should we mark it as EXPERIMENTAL on all
platforms only because some "exotic" (at least SH) platforms have kdump
not very long implemented?
Bernhard
--
Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Bernhard Walle <bwalle@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
vgoyal@redhat.com
Subject: Re: [PATCH] Remove CONFIG_EXPERIMENTAL from kdump
Date: Thu, 26 Jun 2008 10:28:03 +0200 [thread overview]
Message-ID: <20080626102803.2a1a46cd@halley.suse.de> (raw)
In-Reply-To: <20080626012337.a73c91d2.akpm@linux-foundation.org>
* Andrew Morton [2008-06-26 01:23]:
> >
> > config PROC_VMCORE
> > bool "/proc/vmcore support (EXPERIMENTAL)"
> > - depends on PROC_FS && EXPERIMENTAL && CRASH_DUMP
> > + depends on PROC_FS && CRASH_DUMP
> > default y
> > help
> > Exports the dump image of crashed kernel in ELF format.
>
> What about powerpc, sh and ia64?
At least for ia64 I wouldn't consider it as experimental. Don't know
about SH and PPC. But should we mark it as EXPERIMENTAL on all
platforms only because some "exotic" (at least SH) platforms have kdump
not very long implemented?
Bernhard
--
Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development
next prev parent reply other threads:[~2008-06-26 8:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 21:49 [PATCH] Remove CONFIG_EXPERIMENTAL from kdump Bernhard Walle
2008-06-25 21:49 ` Bernhard Walle
2008-06-25 21:52 ` WANG Cong
2008-06-25 21:52 ` WANG Cong
2008-06-25 22:16 ` Vivek Goyal
2008-06-25 22:16 ` Vivek Goyal
2008-06-26 7:23 ` Bernhard Walle
2008-06-26 7:23 ` Bernhard Walle
2008-06-26 7:24 ` Bernhard Walle
2008-06-26 7:24 ` Bernhard Walle
2008-06-26 8:06 ` Ingo Molnar
2008-06-26 8:06 ` Ingo Molnar
2008-06-26 8:23 ` Andrew Morton
2008-06-26 8:23 ` Andrew Morton
2008-06-26 8:28 ` Bernhard Walle [this message]
2008-06-26 8:28 ` Bernhard Walle
2008-06-26 9:11 ` Bernhard Walle
2008-06-26 9:11 ` Bernhard Walle
2008-06-26 12:35 ` Vivek Goyal
2008-06-26 12:35 ` Vivek Goyal
2008-06-26 12:38 ` Bernhard Walle
2008-06-26 12:38 ` Bernhard Walle
2008-06-27 8:13 ` Paul Mundt
2008-06-27 8:13 ` Paul Mundt
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=20080626102803.2a1a46cd@halley.suse.de \
--to=bwalle@suse.de \
--cc=akpm@linux-foundation.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@redhat.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 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.