From: David Miller <davem@davemloft.net>
To: sameo@linux.intel.com
Cc: netdev@vger.kernel.org
Subject: Re: [GIT] [3.20] NFC update
Date: Wed, 28 Jan 2015 22:50:19 -0800 (PST) [thread overview]
Message-ID: <20150128.225019.1581863333410734561.davem@davemloft.net> (raw)
In-Reply-To: <20150129005216.GA1137@ribalta.ger.corp.intel.com>
From: Samuel Ortiz <sameo@linux.intel.com>
Date: Thu, 29 Jan 2015 01:52:16 +0100
> This is the first NFC pull request for 3.20.
>
> With this one we have:
>
> - Secure element support for the ST Micro st21nfca driver. This depends
> on a few HCI internal changes in order for example to support more
> than one secure element per controller.
>
> - ACPI support for NXP's pn544 HCI driver. This controller is found on
> many x86 SoCs and is typically enumerated on the ACPI bus there.
>
> - A few st21nfca and st21nfcb fixes. Since they're not critical fixes,
> I assumed it's too late for a 3.19 inclusion. Please let me know if
> you'd prefer to see them going through a net pull request instead.
Applied, thanks Samuel.
next prev parent reply other threads:[~2015-01-29 6:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 0:52 [GIT] [3.20] NFC update Samuel Ortiz
2015-01-29 6:50 ` David Miller [this message]
2015-01-29 7:02 ` David Miller
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=20150128.225019.1581863333410734561.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sameo@linux.intel.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;
as well as URLs for NNTP newsgroup(s).