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: <CAA8EJppv+SKVjAf8HdNdBo1e6XuhBBGuGTiVzDEW7kqPwOvXwQ@mail.gmail.com>
Date: Thu, 25 Jul 2024 21:46:19 +0300
From: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
To: Andrew Halaney <ahalaney@...hat.com>
Cc: Bjorn Andersson <andersson@...nel.org>, Konrad Dybcio <konrad.dybcio@...aro.org>, 
	Chris Lew <quic_clew@...cinc.com>, linux-arm-msm@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] soc: qcom: pd-mapper: Depend on ARCH_QCOM || COMPILE_TEST

On Thu, 25 Jul 2024 at 19:23, Andrew Halaney <ahalaney@...hat.com> wrote:
>
> The pd-mapper driver doesn't make sense on non Qualcomm systems. Let's
> follow suit with the rest of the Qualcomm SoC Kconfigs and depend on
> ARCH_QCOM || COMPILE_TEST to avoid asking users about a config they will
> not use.
>
> Fixes: 1ebcde047c54 ("soc: qcom: add pd-mapper implementation")
> Signed-off-by: Andrew Halaney <ahalaney@...hat.com>
> ---
> I *think* this makes sense, but please let me know if you think I'm
> wrong. I was dealing with sorting out new configs for fedora and noticed
> this was being asked for x86, etc, which didn't seem right to me.
> ---
>  drivers/soc/qcom/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

I think this makes sense.

Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>

-- 
With best wishes
Dmitry

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ