From: Samuel Ortiz <sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: Christophe Ricard
<christophe.ricard-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-nfc-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org,
christophe-h.ricard-qxv4g6HH51o@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 0/3] Adding ST21NFCB NCI NFC controller support
Date: Wed, 23 Jul 2014 00:27:07 +0200 [thread overview]
Message-ID: <20140722222707.GB455@zurbaran> (raw)
In-Reply-To: <1401050140-15050-1-git-send-email-christophe-h.ricard-qxv4g6HH51o@public.gmane.org>
Hi Christophe,
On Sun, May 25, 2014 at 10:35:37PM +0200, Christophe Ricard wrote:
> Hi,
>
> Please find a new patchset bringing ST21NFCB support in Reader/Writer and P2P mode.
>
> This patchset apply against:
> 7974728094d35f38775417a26d8f30ea3602496a
> NFC: st21nfca: Add ISO15693 Reader/Writer support
Those 3 and the 4th (code cleanup) applied to nfc-next.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2014-07-22 22:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-25 20:35 [PATCH 0/3] Adding ST21NFCB NCI NFC controller support Christophe Ricard
[not found] ` <1401050140-15050-1-git-send-email-christophe-h.ricard-qxv4g6HH51o@public.gmane.org>
2014-05-25 20:35 ` [PATCH 1/3] NFC: st21nfcb: Add driver for STMicroelectronics ST21NFCB NFC chip Christophe Ricard
2014-05-25 20:35 ` [PATCH 2/3] NFC: dts: st21nfcb_i2c: Add DTS Documentation Christophe Ricard
2014-05-25 20:35 ` [PATCH 3/3] NFC: nci: Add T1T support notification Christophe Ricard
2014-07-22 22:27 ` Samuel Ortiz [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=20140722222707.GB455@zurbaran \
--to=sameo-vuqaysv1563yd54fqh9/ca@public.gmane.org \
--cc=christophe-h.ricard-qxv4g6HH51o@public.gmane.org \
--cc=christophe.ricard-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nfc-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.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).