From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Martin Zaťovič" <m.zatovic1@gmail.com>, linux-kernel@vger.kernel.org
Cc: devicetree@vger.kernel.org, mani@kernel.org,
hemantk@codeaurora.org, elder@linaro.org, f.fainelli@gmail.com,
linus.walleij@linaro.org, Michael.Srba@seznam.cz,
jeffrey.l.hugo@gmail.com, gregkh@linuxfoundation.org,
bjorn.andersson@linaro.org, saravanak@google.com,
krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org
Subject: Re: [PATCH RFC v1 2/2] devicetree: bindings: bus: add Wiegand driver documentation
Date: Thu, 28 Jul 2022 18:43:27 +0200 [thread overview]
Message-ID: <33cd5fd3-f673-4d46-b063-e3615a648d6c@linaro.org> (raw)
In-Reply-To: <20220728091712.13395-2-m.zatovic1@gmail.com>
On 28/07/2022 11:17, Martin Zaťovič wrote:
> Wiegand write-only driver requires definitions of two GPIO lines
> in the devicetree. This adds the documentation of their
> definitions.
>
> Signed-off-by: Martin Zaťovič <m.zatovic1@gmail.com>
You didn't test the bindings, did you?
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-07-28 16:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 9:17 [PATCH RFC v1 1/2] bus: add Wiegand write-only GPIO driver Martin Zaťovič
2022-07-28 9:17 ` [PATCH RFC v1 2/2] devicetree: bindings: bus: add Wiegand driver documentation Martin Zaťovič
2022-07-28 10:15 ` Krzysztof Kozlowski
2022-07-28 13:47 ` Rob Herring
2022-07-28 16:43 ` Krzysztof Kozlowski [this message]
2022-08-22 7:21 ` Linus Walleij
2022-07-28 9:56 ` [PATCH RFC v1 1/2] bus: add Wiegand write-only GPIO driver Greg KH
2022-07-28 10:05 ` Greg KH
2022-07-28 10:32 ` Krzysztof Kozlowski
2022-08-22 7:14 ` Linus Walleij
[not found] ` <CAPGNi94R6bW80Yc=B5iesW=ihxy_bD1p-iPhLCASh_=82mjT9w@mail.gmail.com>
2022-09-20 9:44 ` Linus Walleij
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=33cd5fd3-f673-4d46-b063-e3615a648d6c@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Michael.Srba@seznam.cz \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=elder@linaro.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hemantk@codeaurora.org \
--cc=jeffrey.l.hugo@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.zatovic1@gmail.com \
--cc=mani@kernel.org \
--cc=robh+dt@kernel.org \
--cc=saravanak@google.com \
/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
all inboxes | Powered by JetHome®