linux-kernel - Re: Situation of CONFIG_CLK_SUNXI_PRCM

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: <10272596.nUPlyArG6x@jernej-laptop>
Date:   Wed, 10 May 2023 22:54:32 +0200
From:   Jernej Škrabec <jernej.skrabec@...il.com>
To:     Chen-Yu Tsai <wens@...e.org>, Samuel Holland <samuel@...lland.org>,
        linux-sunxi@...ts.linux.dev, linux-clk@...r.kernel.org,
        kernel-janitors <kernel-janitors@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Lukas Bulwahn <lukas.bulwahn@...il.com>
Subject: Re: Situation of CONFIG_CLK_SUNXI_PRCM_SUN9I

Hi Lukas,

Dne sreda, 10. maj 2023 ob 07:38:04 CEST je Lukas Bulwahn napisal(a):
> Dear Maxime,
> 

I don't see Maxime in recipients...

> with commit 49c726d55c1b ("clk: sunxi: Add Kconfig options"), you
> introduce various build configurations for Legacy clock support for
> Allwinner SoCs. Among them, you introduce the config
> CLK_SUNXI_PRCM_SUN9I in drivers/clk/sunxi/Kconfig, but this config is
> not used anywhere in the kernel tree.
> 
> Can we just delete this config CLK_SUNXI_PRCM_SUN9I again, as it is
> not needed, or did you simply miss to adjust the Makefile for this
> option to be effective?

I think this is the best approach. If it wasn't used by now, it can only make 
further mess in distro configs if introduced.

Best regards,
Jernej

> 
> I will gladly send a patch, once you could give me a quick pointer.
> 
> 
> Best regards,
> 
> Lukas
> 
> Note: This is a resent email (see original email:
> https://lore.kernel.org/all/CAKXUXMzqCktKz7vGN4_QAp4n1SeP0-YHL19evmVSfseZOem
> d5g@...l.gmail.com/); now hopefully with an email address for Maxime that
> reaches Maxime.