linux-kernel - Re: [PATCH V3] tty: serial: meson: Fix the compile link error reported by kernel test robot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <8747c5c6-a129-3a26-8ebb-9e21a18236ec@baylibre.com>
Date:   Tue, 1 Mar 2022 08:23:26 +0100
From:   Neil Armstrong <narmstrong@...libre.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Yu Tu <yu.tu@...ogic.com>, linux-serial@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org,
        linux-amlogic@...ts.infradead.org, linux-kernel@...r.kernel.org,
        Jiri Slaby <jirislaby@...nel.org>,
        Kevin Hilman <khilman@...libre.com>,
        Jerome Brunet <jbrunet@...libre.com>,
        Martin Blumenstingl <martin.blumenstingl@...glemail.com>,
        kernel test robot <lkp@...el.com>,
        Dan Carpenter <dan.carpenter@...cle.com>
Subject: Re: [PATCH V3] tty: serial: meson: Fix the compile link error
 reported by kernel test robot

Hi Greg,

Le 28/02/2022 à 22:21, Greg Kroah-Hartman a écrit :
> On Mon, Feb 28, 2022 at 03:13:48PM +0100, Neil Armstrong wrote:
>> Hi,
>>
>> On 28/02/2022 14:55, Yu Tu wrote:
>>> Describes the calculation of the UART baud rate clock using a clock
>>> frame. Forgot to add in Kconfig kernel test Robot compilation error
>>> due to COMMON_CLK dependency.
>>>
>>> Fixes: ("tty: serial:meson: Describes the calculation of the UART baud rate clock using a clock frame“)
>>
>> As I already replied on V2 of this patch, you're invited to apply these fixes directly
>> on the next version of your "Use CCF to describe the UART baud rate clock" patchset
>> and not as a separate patch.
> 
> No, this is broken in linux-next now as the path listed here is in my
> tree right now.

Oh, I wasn't aware you took this patchset.

> 
> I need a fix for it, or I can revert the original.

Please revert the whole patchset, it's not ready yet, neither fully reviewed ands buggy
on old SoCs.

Thanks,
Neil

> 
> thanks,
> 
> greg k-h