linux-kernel - Re: [PATCH 1/9] arm64: dts: hisilicon: hip05: move non-MMIO node out of soc

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]

Date: Wed, 24 Apr 2024 10:37:43 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Wei Xu <xuwei5@...ilicon.com>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
 Conor Dooley <conor+dt@...nel.org>, linux-arm-kernel@...ts.infradead.org,
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: Krzysztof Kozlowski <krzk@...nel.org>
Subject: Re: [PATCH 1/9] arm64: dts: hisilicon: hip05: move non-MMIO node out
 of soc

On 24/04/2024 09:23, Krzysztof Kozlowski wrote:
> On 24/04/2024 09:16, Wei Xu wrote:
>> Hi Krzysztof,
>>
>> On 2024/4/24 14:54, Krzysztof Kozlowski wrote:
>>>
>>> On Tue, 02 Apr 2024 21:31:40 +0200, Krzysztof Kozlowski wrote:
>>>> Non-MMIO devices, which are BTW not really part of the SoC, should not
>>>> be within simple-bus, as reported by dtc W=1 warning:
>>>>
>>>>   hip05.dtsi:301.30-305.5: Warning (simple_bus_reg): /soc/refclk200mhz: missing or empty reg/ranges property
>>>>
>>>>
>>>
>>> Almost a month passed, no replies from maintainers about picking it up. Dunno,
>>> looks abandoned, so let me grab this. If anyone else wants to pick it up, let
>>> me know.
>>>
>>
>> Sorry for the late reply!
>> I am applying these patches which are in the following git repo.
>>   https://github.com/hisilicon/linux-hisi/tree/next/dt64
>>
>> And it is fine to me to go through your git tree.
>> Thanks!
> 
> So you picked them up? Why you did not notify anyone? b4 does it almost
> automatically. How anyone can know what is happening with the patches?
> 
> I will drop them from my tree.

One more thing:

Even though you applied these patches few days ago, they are still not
in linux-next (as of next-20240423), which suggests your tree is not in
next.

Please read entire presentation "Beginner Linux kernel maintainer's
toolbox" from LPC 2023 and improve your workflow by:
1. Properly notifying patch status.
2. Being part of the integration tree.
3. ... and more, as explained in above talk.

There is a link to video and slides:
https://lpc.events/event/17/contributions/1498/

Best regards,
Krzysztof