All of lore.kernel.org
 help / color / mirror / Atom feed
From: ron minnich <rminnich@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Matthew Garrett <mjg59@google.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	"maintainer:X86 ARCHITECTURE..." <x86@kernel.org>,
	lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] x86 support for the initrd= command line option
Date: Mon, 23 Mar 2020 11:54:28 -0700	[thread overview]
Message-ID: <CAP6exYJdCzG5EOPB9uaWz+uG-KKt+j7aJMGMfqqD3vthco_Y_g@mail.gmail.com> (raw)
In-Reply-To: <A814A71D-0450-4724-885B-859BCD2B7CBD@zytor.com>

On Mon, Mar 23, 2020 at 11:19 AM <hpa@zytor.com> wrote:
> Pointing to any number of memory chunks via setup_data works and doesn't need to be exposed to the user, but I guess the above is reasonable.

so, good to go?

>
> *However*, I would also suggest adding "initrdmem=" across architectures that doesn't have the ambiguity.

agreed. I can look at doing that next.

ron

  reply	other threads:[~2020-03-23 18:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-19 23:49 [PATCH 1/1] x86 support for the initrd= command line option ron minnich
2020-03-19 23:57 ` hpa
2020-03-20  0:50   ` ron minnich
2020-03-20  0:59     ` hpa
2020-03-20 15:39       ` ron minnich
2020-03-20 18:19       ` Matthew Garrett
2020-03-23 18:19         ` hpa
2020-03-23 18:54           ` ron minnich [this message]
2020-03-23 19:05             ` hpa
2020-03-23 19:40               ` ron minnich
2020-03-23 21:41                 ` hpa
2020-03-23 22:29                   ` ron minnich
2020-03-23 22:38                     ` ron minnich
2020-03-24 16:05                       ` ron minnich
2020-03-24 16:12                         ` Randy Dunlap
2020-03-24 16:19                           ` ron minnich
2020-03-25 17:21                             ` hpa
2020-04-27  7:35                             ` [tip: x86/boot] x86/setup: Add an initrdmem= option to specify initrd physical address tip-bot2 for Ronald G. Minnich
2020-03-25  3:30                     ` [PATCH 1/1] x86 support for the initrd= command line option H. Peter Anvin
2020-03-25 16:19                       ` ron minnich
2020-03-25 17:20                         ` hpa

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=CAP6exYJdCzG5EOPB9uaWz+uG-KKt+j7aJMGMfqqD3vthco_Y_g@mail.gmail.com \
    --to=rminnich@gmail.com \
    --cc=bp@alien8.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mjg59@google.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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 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.