[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200914160634.GL3956970@smile.fi.intel.com>
Date: Mon, 14 Sep 2020 19:06:34 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Hsin-Yi Wang <hsinyi@...omium.org>
Cc: linux-serial@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jirislaby@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
Serge Semin <Sergey.Semin@...kalelectronics.ru>,
Changqi Hu <changqi.hu@...iatek.com>,
Frank Wunderlich <frank-w@...lic-files.de>,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org,
Enric Balletbo i Serra <enric.balletbo@...labora.com>
Subject: Re: [PATCH 1/2] tty: serial: print earlycon info after match->setup
On Fri, Sep 11, 2020 at 05:39:26PM +0800, Hsin-Yi Wang wrote:
> 8250 devices may modify iotype in their own earlycon setup. For example:
> 8250_mtk and 8250_uniphier force iotype to be MMIO32. Print earlycon info
> after match->setup to reflect actual earlycon info.
But this means you do something which user didn't ask for...
> +static void __init earlycon_info(struct earlycon_device *device)
Can it be earlycon_pr_info() or earlycon_print_info() ?
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists