From: "H. Peter Anvin" <hpa@zytor.com>
To: Tom Rini <trini@konsulko.com>, ron minnich <rminnich@gmail.com>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Borislav Petkov <bp@suse.de>,
Dominik Brodowski <linux@dominikbrodowski.net>
Subject: Re: [PATCH] initrd: Remove erroneous comment
Date: Mon, 22 Jun 2020 14:03:28 -0700 [thread overview]
Message-ID: <5d6dbaf4-26bf-d71a-595e-0b665d4ae614@zytor.com> (raw)
In-Reply-To: <20200622210145.GM27801@bill-the-cat>
On 2020-06-22 14:01, Tom Rini wrote:
>
> I'm picky here because, well, there's a whole lot of moving parts in the
> pre-kernel world. In a strict sense, "UEFI" doesn't do anything with
> the kernel but based on hpa's comments I assume that at least the
> in-kernel UEFI stub does what Documentation/x86/booting.rst suggests to
> do and consumes initrd=/file just like "initrd /file" in extlinux.conf,
> etc do. And since the EFI stub is cross-platform, it's worth noting
> this too.
>
For what it's worth, normally boot loaders don't strip this from the
kernel command line passed to the kernel, although there might be ones
which do so. In general this is bad practice; it is better to let the
initrd show in /proc/cmdline.
-hpa
next prev parent reply other threads:[~2020-06-22 21:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 14:30 [PATCH] initrd: Remove erroneous comment Tom Rini
2020-06-19 17:49 ` [tip: x86/cleanups] " tip-bot2 for Tom Rini
2020-06-20 0:03 ` [PATCH] " ron minnich
2020-06-22 20:23 ` hpa
2020-06-22 20:02 ` ron minnich
2020-06-22 20:40 ` Tom Rini
2020-06-22 20:48 ` H. Peter Anvin
2020-06-22 21:06 ` Tom Rini
2020-06-22 20:56 ` ron minnich
2020-06-22 21:01 ` Tom Rini
2020-06-22 21:03 ` H. Peter Anvin [this message]
2020-06-22 21:07 ` Tom Rini
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=5d6dbaf4-26bf-d71a-595e-0b665d4ae614@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=rminnich@gmail.com \
--cc=trini@konsulko.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;
as well as URLs for NNTP newsgroup(s).