From: Pekka Enberg <penberg@iki.fi>
To: jerry.hoemann@hp.com, Pekka Enberg <penberg@kernel.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Rob Landley <rob@landley.net>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, x86 maintainers <x86@kernel.org>,
Matt Fleming <matt.fleming@intel.com>,
Yinghai Lu <yinghai@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"list@ebiederm.org:DOCUMENTATION" <linux-doc@vger.kernel.org>,
"list@ebiederm.org:MEMORY MANAGEMENT"
<linux-mm@kvack.org>linux-doc@vger.kernel.org,
linux-efi@vger.kernel.org, Vivek Goyal <vgoyal@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] Early use of boot service memory
Date: Fri, 15 Nov 2013 10:36:37 +0200 [thread overview]
Message-ID: <5285DD15.6080700@iki.fi> (raw)
In-Reply-To: <20131115005049.GJ5116@anatevka.fc.hp.com>
On 11/15/13 2:50 AM, jerry.hoemann@hp.com wrote:
> One already has to specify command line arguments to enable kdump.
Yes, so what?
The problem with your patch is that now to enable kdump, I have to know
that there's a second command line option and if my firmware is "broken"
or not. The former is already a problem (how do I even know such a
thing exists?) but the latter is almost impossible to solve from user
point of view. And if I have a "broken" firmware, kdump won't work no
matter what options I pass.
I really don't see what's practical about that.
Pekka
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2013-11-16 14:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1384222558-38527-1-git-send-email-jerry.hoemann@hp.com>
[not found] ` <d73ccce9-6a0d-4470-bda3-f0c6eb96b5e4@email.android.com>
[not found] ` <20131113224503.GB25344@anatevka.fc.hp.com>
[not found] ` <52840206.5020006@zytor.com>
[not found] ` <20131113235708.GC25344@anatevka.fc.hp.com>
[not found] ` <CAOJsxLFkHQ6_f+=CMwfNLykh59TZH5VrWeVEDPCWPF1wiw7tjQ@mail.gmail.com>
[not found] ` <20131114180455.GA32212@anatevka.fc.hp.com>
[not found] ` <CAOJsxLFWMi8DoFp+ufri7XoFO27v+2=0oksh8+NhM6P-OdkOwg@mail.gmail.com>
2013-11-14 18:45 ` [PATCH 0/3] Early use of boot service memory H. Peter Anvin
[not found] ` <20131115005049.GJ5116@anatevka.fc.hp.com>
[not found] ` <20131115062417.GB9237@gmail.com>
[not found] ` <CAE9FiQWzSTtW8N=0hoUe6iCSM-k64Mv97n0whAS0_vZ+psuOsg@mail.gmail.com>
2013-11-15 6:59 ` H. Peter Anvin
2013-11-15 14:07 ` Vivek Goyal
2013-11-15 17:33 ` Yinghai Lu
2013-11-15 17:40 ` H. Peter Anvin
2013-11-15 18:30 ` Vivek Goyal
2013-11-15 18:46 ` H. Peter Anvin
2013-11-15 19:16 ` H. Peter Anvin
2013-11-18 15:22 ` Vivek Goyal
2013-11-18 18:29 ` H. Peter Anvin
2013-11-18 18:52 ` Vivek Goyal
2013-11-19 1:32 ` H. Peter Anvin
2013-11-19 3:02 ` Yinghai Lu
2013-11-15 18:03 ` Vivek Goyal
2013-11-15 22:24 ` Yinghai Lu
2013-11-15 22:55 ` jerry.hoemann
2013-11-15 23:43 ` Yinghai Lu
2013-11-18 15:32 ` Vivek Goyal
2013-11-18 19:34 ` Yinghai Lu
2013-11-18 19:39 ` Vivek Goyal
2013-11-15 18:16 ` jerry.hoemann
2013-11-15 8:36 ` Pekka Enberg [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=5285DD15.6080700@iki.fi \
--to=penberg@iki.fi \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jerry.hoemann@hp.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matt.fleming@intel.com \
--cc=mingo@redhat.com \
--cc=penberg@kernel.org \
--cc=rob@landley.net \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yinghai@kernel.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;
as well as URLs for NNTP newsgroup(s).