linux-kernel - Re: [PATCH v2] MIPS: ralink: define stubs for clk_set

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] [day] [month] [year] [list]

Message-ID: <20210325100057.GE5775@alpha.franken.de>
Date:   Thu, 25 Mar 2021 11:00:57 +0100
From:   Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To:     Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
Cc:     John Crispin <john@...ozen.org>, linux-mips@...r.kernel.org,
        linux-kernel@...r.kernel.org, sergei.shtylyov@...il.com,
        thierry.reding@...il.com, linux-tegra@...r.kernel.org,
        balbi@...nel.org, digetx@...il.com,
        kernel test robot <lkp@...el.com>
Subject: Re: [PATCH v2] MIPS: ralink: define stubs for clk_set_parent to fix
 compile testing

On Wed, Mar 17, 2021 at 12:26:44PM +0100, Krzysztof Kozlowski wrote:
> The Ralink MIPS platform does not use Common Clock Framework and does
> not define certain clock operations leading to compile test failures:
> 
>     /usr/bin/mips-linux-gnu-ld: drivers/usb/phy/phy-tegra-usb.o: in function `tegra_usb_phy_init':
>     phy-tegra-usb.c:(.text+0x1dd4): undefined reference to `clk_get_parent'
> 
> Reported-by: kernel test robot <lkp@...el.com>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
> Acked-by: John Crispin <john@...ozen.org>
> 
> ---
> 
> Changes since v1:
> 1. Use EXPORT_SYMBOL_GPL like two other stubs in the file.
> 2. Add Ack
> ---
>  arch/mips/ralink/clk.c | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)

applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]