linux-kernel - Re: [PATCH] arm64: dts: qcom: c630: Fix firmware paths

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: <CAKXuJqi-ApBGHewYEhnJJR_s-xf5EAfJA2J1ieww9eZjXYFUYQ@mail.gmail.com>
Date:   Mon, 26 Dec 2022 13:23:34 -0600
From:   Steev Klimaszewski <steev@...i.org>
To:     Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Cc:     agross@...nel.org, andersson@...nel.org,
        devicetree@...r.kernel.org, konrad.dybcio@...aro.org,
        krzysztof.kozlowski+dt@...aro.org, linux-arm-msm@...r.kernel.org,
        linux-kernel@...r.kernel.org, robh+dt@...nel.org
Subject: Re: [PATCH] arm64: dts: qcom: c630: Fix firmware paths

On Mon, Dec 26, 2022 at 6:04 AM Krzysztof Kozlowski
<krzysztof.kozlowski@...aro.org> wrote:
>
> On 26/12/2022 01:47, Steev Klimaszewski wrote:
> > The firmware paths were pointing to qcom/manufacturer whereas other
> > devices have them under qcom/chipset/manufacturer, so fix this up on the
> > c630, so we follow the same standard setup.
> >
> > Signed-off-by: Steev Klimaszewski <steev@...i.org>
>
> Do not attach your patches to some other threads. It messes with reading
> and applying.
>
> Best regards,
> Krzysztof
>
Sorry, I screwed up my first patch, and this was supposed to be a v2
of that one.  I'll do better on other submissions.