From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Pali Rohár" <pali@kernel.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: marvell: Update Armada 37xx platform bindings
Date: Sat, 24 Sep 2022 18:53:50 +0200 [thread overview]
Message-ID: <daf1b77c-e752-70d9-c0eb-81d5a9adaa86@linaro.org> (raw)
In-Reply-To: <20220924143004.evsnw3xaplc57aot@pali>
On 24/09/2022 16:30, Pali Rohár wrote:
> On Saturday 24 September 2022 15:50:38 Krzysztof Kozlowski wrote:
>> On 08/08/2022 22:23, Pali Rohár wrote:
>>> PING?
>>>
>>
>> You got the ack, what are you pinging us for?
>>
>> Best regards,
>> Krzysztof
>>
> So, who can take this patch?
This looks like platform bindings, so the platform maintainers. Would be
easier for them to pick it up, if they were CCed. :)
I actually hoped they will pick up also fix for maintainers entry:
https://lore.kernel.org/all/875yi5g96s.fsf@BL-laptop/
...
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-09-24 16:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 20:01 [PATCH] dt-bindings: marvell: Update Armada 37xx platform bindings Pali Rohár
2022-07-18 20:57 ` Rob Herring
2022-08-08 20:23 ` Pali Rohár
2022-08-09 5:58 ` Krzysztof Kozlowski
2022-08-09 13:13 ` Pali Rohár
2022-08-09 15:46 ` Krzysztof Kozlowski
2022-08-09 15:48 ` Pali Rohár
2022-09-24 13:50 ` Krzysztof Kozlowski
2022-09-24 14:30 ` Pali Rohár
2022-09-24 16:53 ` Krzysztof Kozlowski [this message]
2022-08-09 13:12 ` Pali Rohár
2022-08-09 14:58 ` Andrew Lunn
2023-02-01 8:27 ` Gregory CLEMENT
2022-09-24 12:06 ` Pali Rohár
2022-10-09 11:56 ` Pali Rohár
2022-11-01 22:43 ` Pali Rohár
2022-11-28 18:18 ` Pali Rohár
2022-12-16 18:20 ` Pali Rohár
2023-01-22 11:29 ` Pali Rohár
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=daf1b77c-e752-70d9-c0eb-81d5a9adaa86@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali@kernel.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).