linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Lars Poeschel <poeschel@lemonage.de>
Cc: devicetree@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
	"GitAuthor: Lars Poeschel" <poeschel@lemonage.de>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 2/6] nfc: pn532_uart: Add NXP PN532 to devicetree docs
Date: Mon, 5 Nov 2018 13:35:15 -0600	[thread overview]
Message-ID: <20181105193515.GA22755@bogus> (raw)
In-Reply-To: <20181101100216.613-2-poeschel@lemonage.de>

On Thu,  1 Nov 2018 11:02:10 +0100, Lars Poeschel wrote:
> Add a simple binding doc for the pn532.
> 
> Signed-off-by: Lars Poeschel <poeschel@lemonage.de>
> ---
> Changes in v4:
> - Add documentation about reg property in case of i2c
> 
> Changes in v3:
> - seperate binding doc instead of entry in trivial-devices.txt
> 
>  .../devicetree/bindings/nfc/pn532.txt         | 33 +++++++++++++++++++
>  1 file changed, 33 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/nfc/pn532.txt
> 

Reviewed-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2018-11-05 19:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-01 10:02 [PATCH v4 1/6] nfc: pn533: i2c: "pn532" as dt compatible string Lars Poeschel
2018-11-01 10:02 ` [PATCH v4 2/6] nfc: pn532_uart: Add NXP PN532 to devicetree docs Lars Poeschel
2018-11-05 19:35   ` Rob Herring [this message]
2018-11-01 10:02 ` [PATCH v4 3/6] nfc: pn533: Add dev_up/dev_down hooks to phy_ops Lars Poeschel
2018-11-01 10:02 ` [PATCH v4 4/6] nfc: pn533: add UART phy driver Lars Poeschel
2018-11-14 15:35   ` Johan Hovold
2018-12-03 14:26     ` Lars Poeschel
2018-12-05 15:29       ` Johan Hovold
2018-11-01 10:02 ` [PATCH v4 5/6] nfc: pn533: Add autopoll capability Lars Poeschel
2018-11-01 10:02 ` [PATCH v4 6/6] nfc: pn532_uart: Make use of pn532 autopoll Lars Poeschel

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=20181105193515.GA22755@bogus \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=poeschel@lemonage.de \
    /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).