linux-kernel - Re: [PATCH] soc: rockchip: ROCKCHIP_GRF should not default to y, unconditionally

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]

Date:   Fri, 16 Jul 2021 00:42:52 +0200
From:   Heiko Stuebner <heiko@...ech.de>
To:     Geert Uytterhoeven <geert+renesas@...der.be>
Cc:     Heiko Stuebner <heiko@...ech.de>,
        Douglas Anderson <dianders@...omium.org>,
        linux-kernel@...r.kernel.org, linux-rockchip@...ts.infradead.org,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] soc: rockchip: ROCKCHIP_GRF should not default to y, unconditionally

On Mon, 8 Feb 2021 15:38:55 +0100, Geert Uytterhoeven wrote:
> Merely enabling CONFIG_COMPILE_TEST should not enable additional code.
> To fix this, restrict the automatic enabling of ROCKCHIP_GRF to
> ARCH_ROCKCHIP, and ask the user in case of compile-testing.

Applied, thanks!

[1/1] soc: rockchip: ROCKCHIP_GRF should not default to y, unconditionally
      commit: 2a1c55d4762dd34a8b0f2e36fb01b7b16b60735b

I actually found the old one deep down in my inbox some days ago,
so had applied that one already. Hope nothing changed with your
RESEND.


Best regards,
-- 
Heiko Stuebner <heiko@...ech.de>