From: "John W. Linville" <linville@tuxdriver.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Linux Wireless <linux-wireless@vger.kernel.org>,
Linux NFC <linux-nfc@ml01.01.org>
Subject: Re: [GIT] [3.19] NFC update
Date: Thu, 4 Dec 2014 11:28:36 -0500 [thread overview]
Message-ID: <20141204162835.GA2842@tuxdriver.com> (raw)
In-Reply-To: <20141202223749.GA31964@ribalta.ger.corp.intel.com>
On Tue, Dec 02, 2014 at 11:37:49PM +0100, Samuel Ortiz wrote:
> Hi John,
>
> This is the NFC pull request for 3.19.
>
> With this one we get:
>
> - NFC digital improvements for DEP support: Chaining, NACK and ATN
> support added.
>
> - NCI improvements: Support for p2p target, SE IO operand addition,
> SE operands extensions to support proprietary implementations, and
> a few fixes.
>
> - NFC HCI improvements: OPEN_PIPE and NOTIFY_ALL_CLEARED support,
> and SE IO operand addition.
>
> - A bunch of minor improvements and fixes for STMicro st21nfcb and
> st21nfca
>
> Thanks in advance for pulling that one in.
>
>
> The following changes since commit 18ca43823f3ce111c6efb8cc90d9f35246527727:
>
> mwifiex: add Tx status support for ACTION frames (2014-11-25 14:09:57 -0500)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/sameo/nfc-next.git tags/nfc-next-3.19-1
>
> for you to fetch changes up to e479ce479743984a5d4581749f9aaa9c3bfd65e4:
>
> NFC: NCI: Fix max length of General Bytes in ATR_RES (2014-12-02 22:59:28 +0100)
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:[~2014-12-04 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-02 22:37 [GIT] [3.19] NFC update Samuel Ortiz
2014-12-04 16:28 ` 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=20141204162835.GA2842@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.