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: <f7c5c3f9-0083-c0b0-dc49-e66139268312@linaro.org>
Date:   Thu, 21 Apr 2022 10:01:23 +0200
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     Matthias Brugger <matthias.bgg@...il.com>,
        linux-mediatek@...ts.infradead.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] arm64: dts: mt8183-kukui: align SPI NOR node name with
 dtschema

On 20/04/2022 14:35, Matthias Brugger wrote:
> 
> 
> On 20/04/2022 11:10, Krzysztof Kozlowski wrote:
>> On Thu, 7 Apr 2022 16:21:43 +0200, Krzysztof Kozlowski wrote:
>>> The node names should be generic and SPI NOR dtschema expects "flash".
>>>
>>>
>>
>> Looks like no one wants to take this, so let me take care of it.
>>
> 
> First thing would have been a ping on the patch, don't you think? 

And what does it change? The operating-points clean up [1] was sent in
August last year, then in this April, and you responded only when I
wrote pick-up. The Google cros-ec clean up was sent in Feb and two weeks
later pinged [2].

Pinging and resending apparently does not help. It's okay, happens, we
are all extra busy and we all pretty often do it as part of
community/hobby/spare time.

> Anyway as I 
> said the last time, if you take DTS patches for mediatek

I don't want to take the patches for Mediatek. But I also don't want to
resend and ping each one of them because it did not work in the past.

> , I'd need a stable 
> branch I can merge so that we don't have any merge conflicts in the end.

Can you just pick the patch?


[1]
https://lore.kernel.org/all/?q=%22arm64%3A+dts%3A+mediatek%3A+align+operating-points+table+name+with+dtschema%22

[2]
https://lore.kernel.org/all/?q=%22arm64%3A+dts%3A+mt8183%3A+align+Google+CROS+EC+PWM+node+name+with+dtschema%22

Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ