From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh@kernel.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Linux Input <linux-input@vger.kernel.org>,
devicetree@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND PATCH v3 0/3] dt-bindings: input: gpio-keys: apply via DT tree
Date: Tue, 12 Jul 2022 09:11:00 +0200 [thread overview]
Message-ID: <09c11a48-fb3f-8fde-c530-dc13f5cf4bf6@linaro.org> (raw)
In-Reply-To: <YsiuRbaFMa683H1Z@google.com>
On 09/07/2022 00:23, Dmitry Torokhov wrote:
>>> I am sorry but what series/branch this series is based on? I tried
>>> applying but there are conflicts. The latest I have that is touching
>>> gpio-keys.yaml is:
>>>
>>> 4fda8a2df83a dt-bindings: input: use generic node names
>>
>> This one from me:
>>
>> https://lore.kernel.org/all/20220608211207.2058487-1-robh@kernel.org/
>
> Ah, I see, thank you. Applied the lot.
Great! Thank you.
Best regards,
Krzysztof
prev parent reply other threads:[~2022-07-12 7:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 12:03 [RESEND PATCH v3 0/3] dt-bindings: input: gpio-keys: apply via DT tree Krzysztof Kozlowski
2022-07-05 12:03 ` [RESEND PATCH v3 1/3] dt-bindings: input: gpio-keys: enforce node names to match all properties Krzysztof Kozlowski
2022-07-05 12:03 ` [RESEND PATCH v3 2/3] dt-bindings: input: gpio-keys: reference input.yaml and document properties Krzysztof Kozlowski
2022-07-05 12:03 ` [RESEND PATCH v3 3/3] dt-bindings: input: gpio-keys: accept also interrupt-extended Krzysztof Kozlowski
2022-07-05 19:11 ` [RESEND PATCH v3 0/3] dt-bindings: input: gpio-keys: apply via DT tree Rob Herring
2022-07-06 6:30 ` Krzysztof Kozlowski
2022-07-08 20:35 ` Dmitry Torokhov
2022-07-08 22:05 ` Rob Herring
2022-07-08 22:23 ` Dmitry Torokhov
2022-07-12 7:11 ` Krzysztof Kozlowski [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=09c11a48-fb3f-8fde-c530-dc13f5cf4bf6@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-input@vger.kernel.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).