linux-kernel - Config REGULATOR_MTK_DVFSR depends on the non-existing config MTK

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

Message-ID: <CAKXUXMx0kMruMNfAv-Os1VSrgfg2vyKv17uDVq-QqB1Szwu+1w@mail.gmail.com>
Date:   Wed, 22 Dec 2021 10:24:58 +0100
From:   Lukas Bulwahn <lukas.bulwahn@...il.com>
To:     Henry Chen <henryc.chen@...iatek.com>
Cc:     Liam Girdwood <lgirdwood@...il.com>,
        Mark Brown <broonie@...nel.org>,
        Matthias Brugger <matthias.bgg@...il.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        linux-mediatek@...ts.infradead.org
Subject: Config REGULATOR_MTK_DVFSR depends on the non-existing config MTK_DVFSRC

Dear Henry,

In commit a0db6b0aa670 ("regulator: Regulator driver for the Mediatek
DVFSRC"), you have added the MediaTek DVFSRC regulator driver with the
config REGULATOR_MTK_DVFSR, which depends on the non-existing config
MTK_DVFSRC.

However, the config MTK_DVFSRC was never introduced in the kernel
repository so far. This makes this whole driver effectively dead code
in the repository.

Do you intend to add a further config MTK_DVFSRC for this driver to be
compiled or can we simply drop this dead driver code?

Best regards,

Lukas