linux-kernel - Re: [PATCH] MAINTAINERS: qcom: Add reviewer for Qualcomm Chromebooks

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: <6a937870-af8c-95fb-1ac3-68e9eb2cbf27@linaro.org>
Date:   Tue, 4 Apr 2023 19:46:56 +0200
From:   Konrad Dybcio <konrad.dybcio@...aro.org>
To:     Douglas Anderson <dianders@...omium.org>,
        Bjorn Andersson <andersson@...nel.org>
Cc:     linux-arm-msm@...r.kernel.org, cros-qcom-dts-watchers@...omium.org,
        Stephen Boyd <swboyd@...omium.org>,
        Matthias Kaehlcke <mka@...omium.org>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MAINTAINERS: qcom: Add reviewer for Qualcomm Chromebooks



On 30.03.2023 23:11, Douglas Anderson wrote:
> Developers on the ChromeOS team generally want to be notified to
> review changes that affect Chromebook device tree files. While we
> could individually add developers, the set of developers and the time
> each one has available to review patches will change over time. Let's
> try adding a group list as a reviewer and see if that's an effective
> way to manage things.
> 
> A few notes:
> * Though this email address is actually backed by a mailing list, I'm
>   adding it as "R"eviewer and not "L"ist since it's not a publicly
>   readable mailing list and it's intended just to have a few people on
>   it. This also hopefully conveys a little more responisbility for the
>   people that are part of this group.
> * I've added all sc7180 and sc7280 files here. At the moment I'm not
>   aware of any non-Chromebooks being supported that use these
>   chips. If later something shows up then we can try to narrow down.
IMO it'd be good if you could keep an eye on all of them, especially
with the quite numerous ways that CrOS fw differs! You're the main
users of the SC7xxx SoCs so it only sounds logical.

> * I've added "sdm845-cheza" to this list but not the rest of
>   "sdm845". Cheza never shipped but some developers still find the old
>   developer boards useful and thus it continues to get minimal
>   maintenance. Most sdm845 device tree work, however, seems to be for
>   non-Chromebooks.
Seems to also still be used in mesa CI

> 
> Cc: Stephen Boyd <swboyd@...omium.org>
> Cc: Matthias Kaehlcke <mka@...omium.org>
> Signed-off-by: Douglas Anderson <dianders@...omium.org>
> ---
Acked-by: Konrad Dybcio <konrad.dybcio@...aro.org>

Konrad
> 
>  MAINTAINERS | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 8d5bc223f305..b4e9c5bda234 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2604,6 +2604,12 @@ F:	include/dt-bindings/*/qcom*
>  F:	include/linux/*/qcom*
>  F:	include/linux/soc/qcom/
>  
> +ARM/QUALCOMM CHROMEBOOK SUPPORT
> +R:	cros-qcom-dts-watchers@...omium.org
> +F:	arch/arm64/boot/dts/qcom/sc7180*
> +F:	arch/arm64/boot/dts/qcom/sc7280*
> +F:	arch/arm64/boot/dts/qcom/sdm845-cheza*
> +
>  ARM/RDA MICRO ARCHITECTURE
>  M:	Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
>  L:	linux-arm-kernel@...ts.infradead.org (moderated for non-subscribers)