From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: David Heidelberg <david@ixit.cz>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Rob Herring <robh+dt@kernel.org>
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, ~okias/devicetree@lists.sr.ht
Subject: Re: [PATCH v3] dt-bindings: net: nfc: nxp,pn544: Convert txt bindings to yaml
Date: Sun, 10 Oct 2021 16:27:35 +0200 [thread overview]
Message-ID: <5fab38bd-33fa-e0bc-5625-e972008f4c97@canonical.com> (raw)
In-Reply-To: <20211009161941.41634-1-david@ixit.cz>
On 09/10/2021 18:19, David Heidelberg wrote:
> Convert bindings for NXP PN544 NFC driver to YAML syntax.
>
> Signed-off-by: David Heidelberg <david@ixit.cz>
> ---
> v2
> - Krzysztof is a maintainer
> - pintctrl dropped
> - 4 space indent for example
> - nfc node name
> v3
> - remove whole pinctrl
> .../bindings/net/nfc/nxp,pn544.yaml | 61 +++++++++++++++++++
> .../devicetree/bindings/net/nfc/pn544.txt | 33 ----------
> 2 files changed, 61 insertions(+), 33 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/net/nfc/nxp,pn544.yaml
> delete mode 100644 Documentation/devicetree/bindings/net/nfc/pn544.txt
>
Rob,
The netdev folks marked patch as not-applicable, so I guess they expect
you to pick it up.
Can you take it? Similarly to my NFC bindings conversion sent this weekend:
https://lore.kernel.org/linux-nfc/20211010142317.168259-1-krzysztof.kozlowski@canonical.com/T/#t
Best regards,
Krzysztof
next prev parent reply other threads:[~2021-10-10 14:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 16:19 David Heidelberg
2021-10-09 17:20 ` Krzysztof Kozlowski
2021-10-10 14:27 ` Krzysztof Kozlowski [this message]
2021-10-10 19:31 ` Rob Herring
2021-10-10 21:01 ` Krzysztof Kozlowski
2021-10-17 16:18 ` David Heidelberg
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=5fab38bd-33fa-e0bc-5625-e972008f4c97@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=davem@davemloft.net \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=~okias/devicetree@lists.sr.ht \
/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®