linux-kernel - Re: [PATCH 0/3] arm64: dts: qcom: msm8916/39: Fix-ups for dynamic reserved mem patches

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: <ZQ8EJIakfFw_cNJm@gerhold.net>
Date:   Sat, 23 Sep 2023 17:28:36 +0200
From:   Stephan Gerhold <stephan@...hold.net>
To:     Bryan O'Donoghue <bryan.odonoghue@...aro.org>
Cc:     Bjorn Andersson <andersson@...nel.org>,
        Andy Gross <agross@...nel.org>,
        Konrad Dybcio <konrad.dybcio@...aro.org>,
        linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] arm64: dts: qcom: msm8916/39: Fix-ups for dynamic
 reserved mem patches

On Sat, Sep 23, 2023 at 04:12:25PM +0100, Bryan O'Donoghue wrote:
> On 21/09/2023 19:56, Stephan Gerhold wrote:
> > Enable GPU/WCNSS properly in some MSM8916/MSM8939 boards that were
> > changed after I sent the patches for the dynamic reserved memory
> > allocation.
> > 
> > I have magic scripts that make the necessary changes automatically so
> > I'm quite sure that I caught all new instances that need adjustment. :-)
> > 
> > Since my scripts only work properly on board DTs with sorted nodes
> > I also included a bonus patch to fix that in some of the MSM8916 DTs.
> > 
> > Signed-off-by: Stephan Gerhold <stephan@...hold.net>
> > ---
> > Stephan Gerhold (3):
> >        arm64: dts: qcom: msm8916-samsung-gt5: Enable GPU
> >        arm64: dts: qcom: msm8939-longcheer-l9100: Enable wcnss_mem
> >        arm64: dts: qcom: msm8916-*: Fix alphabetic node order
> > 
> >   .../boot/dts/qcom/msm8916-alcatel-idol347.dts      |  8 ++---
> >   .../boot/dts/qcom/msm8916-samsung-a3u-eur.dts      | 10 +++---
> >   .../boot/dts/qcom/msm8916-samsung-gt5-common.dtsi  | 38 +++++++++++-----------
> >   arch/arm64/boot/dts/qcom/msm8916-samsung-gt510.dts |  4 +++
> >   arch/arm64/boot/dts/qcom/msm8916-samsung-gt58.dts  |  4 +++
> >   arch/arm64/boot/dts/qcom/msm8916-thwc-uf896.dts    |  8 ++---
> >   arch/arm64/boot/dts/qcom/msm8916-thwc-ufi001c.dts  |  8 ++---
> >   .../arm64/boot/dts/qcom/msm8916-yiming-uz801v3.dts |  8 ++---
> >   .../boot/dts/qcom/msm8939-longcheer-l9100.dts      |  4 +++
> >   9 files changed, 52 insertions(+), 40 deletions(-)
> > ---
> > base-commit: a35461d47fe3e555602912b905f1bae7045256eb
> > change-id: 20230921-msm8916-rmem-fixups-46ec18b9ba5d
> > 
> 
> Do these Fixes shas exist ? I can't seem to find them.
> 

Yes, fetch for-next from
https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git

It did not end up in linux-next yet because the ARM32 build in the
qcom tree is broken currently [1].

[1]: https://lore.kernel.org/linux-next/20230921084252.3c5ab501@canb.auug.org.au/