From: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>
Subject: Re: [PATCH 1/4] arm64: dts: uniphier: ld11-global: use generic node name for audio-codec
Date: Thu, 25 Apr 2024 09:12:17 +0900 [thread overview]
Message-ID: <612963b3-2bca-4ec7-91bc-03b2b6b3f6a4@socionext.com> (raw)
In-Reply-To: <171394159879.43787.1190606574458902919.b4-ty@linaro.org>
Hi Krzysztof,
On 2024/04/24 15:54, Krzysztof Kozlowski wrote:
>
> On Mon, 01 Apr 2024 16:09:49 +0200, Krzysztof Kozlowski wrote:
>> Devicetree specification expects node names to be generic, representing
>> the class of devices.
>>
>>
>
> 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, I couldn't reply your patches due to some problems.
They looks to me, so you can keep on picking them up.
Thank you,
---
Best Regards
Kunihiko Hayashi
prev parent reply other threads:[~2024-04-25 0:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 14:09 [PATCH 1/4] arm64: dts: uniphier: ld11-global: use generic node name for audio-codec Krzysztof Kozlowski
2024-04-01 14:09 ` [PATCH 2/4] arm64: dts: uniphier: ld11-global: drop audio codec port unit address Krzysztof Kozlowski
2024-04-01 14:09 ` [PATCH 3/4] arm64: dts: uniphier: ld20-global: use generic node name for audio-codec Krzysztof Kozlowski
2024-04-01 14:09 ` [PATCH 4/4] arm64: dts: uniphier: ld20-global: drop audio codec port unit address Krzysztof Kozlowski
2024-04-24 6:54 ` [PATCH 1/4] arm64: dts: uniphier: ld11-global: use generic node name for audio-codec Krzysztof Kozlowski
2024-04-25 0:12 ` Kunihiko Hayashi [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=612963b3-2bca-4ec7-91bc-03b2b6b3f6a4@socionext.com \
--to=hayashi.kunihiko@socionext.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=mhiramat@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 read-only IMAP folder(s) and NNTP newsgroup(s).