From: Samuel Ortiz <sameo@linux.intel.com>
To: Michael Thalmeier <michael.thalmeier@hale.at>
Cc: Lauro Ramos Venancio <lauro.venancio@openbossa.org>,
Aloisio Almeida Jr <aloisio.almeida@openbossa.org>,
linux-kernel@vger.kernel.org, linux-nfc@ml01.01.org,
michael@thalmeier.at
Subject: Re: [PATCH] nfc: pn533: Add device tree documentation for i2c phy
Date: Sun, 1 May 2016 23:36:59 +0200 [thread overview]
Message-ID: <20160501213659.GA19653@zurbaran.home> (raw)
In-Reply-To: <1460385362-21986-1-git-send-email-michael.thalmeier@hale.at>
Hi Michael,
On Mon, Apr 11, 2016 at 04:36:02PM +0200, Michael Thalmeier wrote:
> Add pn533-i2c phy devicetree documentation
>
> Signed-off-by: Michael Thalmeier <michael.thalmeier@hale.at>
> ---
> .../devicetree/bindings/net/nfc/pn533-i2c.txt | 31 ++++++++++++++++++++++
> 1 file changed, 31 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/net/nfc/pn533-i2c.txt
Thanks. Applied and pushed.
Cheers,
Samuel.
next prev parent reply other threads:[~2016-05-01 21:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 14:46 [RFC 0/4] NFC: pn533: support for pn532 via I2C Michael Thalmeier
2016-03-25 14:46 ` [RFC 1/4] NFC: pn533: Send ATR_REQ only if NFC_PROTO_NFC_DEP bit is set in poll_protocols Michael Thalmeier
2016-03-25 14:46 ` [RFC 2/4] NFC: pn533: fix deadlock when socket is closed while processing command Michael Thalmeier
2016-03-25 14:46 ` [RFC 3/4] NFC: pn533: Separate pn533 driver in HW dependant and independant parts Michael Thalmeier
2016-03-25 14:46 ` [RFC 4/4] NFC: pn533: add I2C phy driver Michael Thalmeier
2016-04-09 21:45 ` Samuel Ortiz
2016-04-11 14:36 ` [PATCH] nfc: pn533: Add device tree documentation for i2c phy Michael Thalmeier
2016-05-01 21:36 ` Samuel Ortiz [this message]
2016-05-04 15:22 ` [RFC 4/4] NFC: pn533: add I2C phy driver Olliver Schinagl
2016-04-09 21:45 ` [RFC 0/4] NFC: pn533: support for pn532 via I2C Samuel Ortiz
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=20160501213659.GA19653@zurbaran.home \
--to=sameo@linux.intel.com \
--cc=aloisio.almeida@openbossa.org \
--cc=lauro.venancio@openbossa.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfc@ml01.01.org \
--cc=michael.thalmeier@hale.at \
--cc=michael@thalmeier.at \
/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®