From: Tom Rini <trini@konsulko.com>
To: Michael Trimarchi <michael@amarulasolutions.com>
Cc: Yegor Yefremov <yegorslists@googlemail.com>,
Marcin Niestroj <m.niestroj@grinn-global.com>,
Ariel D'Alessandro <ariel.dalessandro@collabora.com>,
Chris Packham <judge.packham@gmail.com>,
Wolfgang Denk <wd@denx.de>, Stefan Roese <sr@denx.de>,
Rick Chen <rick@andestech.com>, Heiko Schocher <hs@denx.de>,
Simon Glass <sjg@chromium.org>, Lokesh Vutla <lokeshvutla@ti.com>,
open list <u-boot@lists.denx.de>,
linux-amarula@amarulasolutions.com
Subject: Re: [PATCH V2] include/configs: Remove rootwait=1 to all the affected boards
Date: Tue, 7 Jun 2022 12:47:50 -0400 [thread overview]
Message-ID: <20220607164750.GV2484912@bill-the-cat> (raw)
In-Reply-To: <20220522132209.100309-1-michael@amarulasolutions.com>
[-- Attachment #1: Type: text/plain, Size: 595 bytes --]
On Sun, May 22, 2022 at 03:22:08PM +0200, Michael Trimarchi wrote:
> rootwait=1 is not a valid kernel boot parameters. According
> to the documenation is only rootwait
>
> rootwait [KNL] Wait (indefinitely) for root device to show up.
> Useful for devices that are detected asynchronously
> (e.g. USB and MMC devices).
>
> Fix:
> Unknown kernel command line parameters "rootwait=1", will be passed to user space.
>
> Signed-off-by: Michael Trimarchi <michael@amarulasolutions.com>
> Reviewed-by: Heiko Schocher <hs@denx.de>
Applied to u-boot/next, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2022-06-07 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-22 13:22 [PATCH V2] include/configs: Remove rootwait=1 to all the affected boards Michael Trimarchi
2022-05-23 4:34 ` Heiko Schocher
2022-06-07 16:47 ` Tom Rini [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=20220607164750.GV2484912@bill-the-cat \
--to=trini@konsulko.com \
--cc=ariel.dalessandro@collabora.com \
--cc=hs@denx.de \
--cc=judge.packham@gmail.com \
--cc=linux-amarula@amarulasolutions.com \
--cc=lokeshvutla@ti.com \
--cc=m.niestroj@grinn-global.com \
--cc=michael@amarulasolutions.com \
--cc=rick@andestech.com \
--cc=sjg@chromium.org \
--cc=sr@denx.de \
--cc=u-boot@lists.denx.de \
--cc=wd@denx.de \
--cc=yegorslists@googlemail.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