From: "John W. Linville" <linville@tuxdriver.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Linux NFC <linux-nfc@ml01.01.org>,
Linux Wireless <linux-wireless@vger.kernel.org>
Subject: Re: [GIT] [3.12] NFC updates
Date: Thu, 15 Aug 2013 15:56:10 -0400 [thread overview]
Message-ID: <20130815195610.GG2133@tuxdriver.com> (raw)
In-Reply-To: <20130814230448.GB11055@zurbaran>
On Thu, Aug 15, 2013 at 01:04:48AM +0200, Samuel Ortiz wrote:
> Hi John,
>
> This is the first NFC pull request for the 3.12 release.
>
> With this one we have:
>
> - A few pn533 improvements and minor fixes. Testing our pn533 driver
> against Google's NCI stack triggered a few issues that we fixed now.
> We also added Tx fragmentation support to this driver.
>
> - More NFC secure element handling. We added a GET_SE netlink command
> for getting all the discovered secure elements, and we defined 2
> additional secure element netlink event (transaction and connectivity).
> We also fixed a couple of typos and copy-paste bugs from the secure
> element handling code.
>
> - Firmware download support for the pn544 driver. This chipset can enter a
> special mode where it's waiting for firmware blobs to replace the
> already flashed one. We now support that mode.
>
> The following changes since commit d1e2586f484dfc36eee2b2d3a6c6c77be67ca492:
>
> mwifiex: fix build error when CONFIG_PM is not set (2013-08-12 14:36:55 -0400)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/sameo/nfc-next.git tags/nfc-next-3.12-1
>
> for you to fetch changes up to 39525ee1dc78ca1f5f2fb1f764f7a141005fe440:
>
> NFC: Update secure element state (2013-08-14 01:13:40 +0200)
Pulling now...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2013-08-15 20:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 23:04 [GIT] [3.12] NFC updates Samuel Ortiz
2013-08-15 3:07 ` Joe Perches
2013-08-16 15:20 ` Samuel Ortiz
2013-08-15 19:56 ` John W. Linville [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=20130815195610.GG2133@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-nfc@ml01.01.org \
--cc=linux-wireless@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).