[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YrrsNSI4+Gbjt9bm@kroah.com>
Date: Tue, 28 Jun 2022 13:55:33 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Michael Walle <michael@...le.cc>
Cc: Rob Herring <robh+dt@...nel.org>,
Frank Rowand <frowand.list@...il.com>,
Jiri Slaby <jirislaby@...nel.org>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org
Subject: Re: [PATCH v2] earlycon: prevent multiple register_console()
On Tue, Jun 28, 2022 at 01:21:23PM +0200, Michael Walle wrote:
> Hi,
>
> Am 2022-06-02 11:00, schrieb Michael Walle:
> > If the earlycon parameter is given twice, the kernel will spit out a
> > WARN() in register_console() because it was already registered. The
> > non-dt variant setup_earlycon() already handles that gracefully. The dt
> > variant of_setup_earlycon() doesn't. Add the check there and add the
> > -EALREADY handling in early_init_dt_scan_chosen_stdout().
> >
> > FWIW, this doesn't happen if CONFIG_ACPI_SPCR_TABLE is set. In that case
> > the registration is delayed until after earlycon parameter(s) are
> > parsed.
> >
> > Signed-off-by: Michael Walle <michael@...le.cc>
>
> Ping :) Or do I have to resend this patch?
I do not see it in my queue anywhere.
Powered by blists - more mailing lists