From: Wei Xu <xuwei5@hisilicon.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: [PATCH 1/9] arm64: dts: hisilicon: hip05: move non-MMIO node out of soc
Date: Thu, 25 Apr 2024 19:12:11 +0800 [thread overview]
Message-ID: <662A3A8B.8030602@hisilicon.com> (raw)
In-Reply-To: <6ce7bc63-1c47-4e3d-a3af-8f229f1c36f7@linaro.org>
Hi Krzysztof,
On 2024/4/24 16:37, Krzysztof Kozlowski wrote:
> 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.
Series applied to the HiSilicon arm64 dt tree:
https://github.com/hisilicon/linux-hisi/tree/next/dt64
>
> 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/
I have went through your slide which is very helpful and detailed.
Thanks!
Best Regards,
Wei
>
> Best regards,
> Krzysztof
>
> .
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2024-04-25 11:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 19:31 [PATCH 1/9] arm64: dts: hisilicon: hip05: move non-MMIO node out of soc Krzysztof Kozlowski
2024-04-02 19:31 ` [PATCH 2/9] arm64: dts: hisilicon: hip05-d02: correct local-bus unit addresses Krzysztof Kozlowski
2024-04-02 19:31 ` [PATCH 3/9] arm64: dts: hisilicon: hip06: move non-MMIO node out of soc Krzysztof Kozlowski
2024-04-02 19:31 ` [PATCH 4/9] arm64: dts: hisilicon: hip06: correct unit addresses Krzysztof Kozlowski
2024-04-02 19:31 ` [PATCH 5/9] arm64: dts: hisilicon: hip07: move non-MMIO node out of soc Krzysztof Kozlowski
2024-04-02 19:31 ` [PATCH 6/9] arm64: dts: hisilicon: hip07: correct unit addresses Krzysztof Kozlowski
2024-04-02 19:31 ` [PATCH 7/9] arm64: dts: hisilicon: hi6220-hikey: add missing port@0 reg Krzysztof Kozlowski
2024-04-02 19:31 ` [PATCH 8/9] arm64: dts: hisilicon: hi6220-hikey: drop unit addresses from fixed regulators Krzysztof Kozlowski
2024-04-02 19:31 ` [PATCH 9/9] arm64: dts: hisilicon: hi6220: correct tsensor unit addresses Krzysztof Kozlowski
2024-04-24 6:54 ` [PATCH 1/9] arm64: dts: hisilicon: hip05: move non-MMIO node out of soc Krzysztof Kozlowski
2024-04-24 7:16 ` Wei Xu
2024-04-24 7:23 ` Krzysztof Kozlowski
2024-04-24 8:37 ` Krzysztof Kozlowski
2024-04-24 9:16 ` Wei Xu
2024-04-25 11:12 ` Wei Xu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=662A3A8B.8030602@hisilicon.com \
--to=xuwei5@hisilicon.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).