From: Matthias Brugger <matthias.bgg@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: dts: mt8183-kukui: align SPI NOR node name with dtschema
Date: Fri, 22 Apr 2022 11:13:27 +0200 [thread overview]
Message-ID: <234d411c-1386-d661-71e3-f1f30f5cbf36@gmail.com> (raw)
In-Reply-To: <f7c5c3f9-0083-c0b0-dc49-e66139268312@linaro.org>
Hi Krzysztof,
On 21/04/2022 10:01, Krzysztof Kozlowski wrote:
> 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].
>
That I answered to the pick-up is just plain coincidence that I had some time to
look into the patches. Sorry for being unresponsive. I'm happy that you care
about MediaTek patches. If you think there will more patches in this cycle or
future cycles, we can also agree on you taking the patches and send me a pull
request later. I only want to avoid any merge conflicts, that's all.
> 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?
>
I pushed it to v5.18-next/dts64 [1]
Let me know if there are other patches that you want me to take.
Regards,
Matthias
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/matthias.bgg/linux.git/log/?h=v5.18-next/dts64
>
> [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
next prev parent reply other threads:[~2022-04-22 9:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 14:21 [PATCH] arm64: dts: mt8183-kukui: align SPI NOR node name with dtschema Krzysztof Kozlowski
2022-04-20 9:10 ` Krzysztof Kozlowski
2022-04-20 12:35 ` Matthias Brugger
2022-04-21 8:01 ` Krzysztof Kozlowski
2022-04-22 9:13 ` Matthias Brugger [this message]
2022-04-22 10:19 ` Krzysztof Kozlowski
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=234d411c-1386-d661-71e3-f1f30f5cbf36@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=devicetree@vger.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=linux-mediatek@lists.infradead.org \
--cc=robh+dt@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).