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.18] NFC update
Date: Fri, 26 Sep 2014 13:38:19 -0400 [thread overview]
Message-ID: <20140926173818.GG22967@tuxdriver.com> (raw)
In-Reply-To: <20140924003423.GF4235@zurbaran>
On Wed, Sep 24, 2014 at 02:34:23AM +0200, Samuel Ortiz wrote:
> Hi John,
>
> This is the NFC pull request for 3.18.
>
> We've had major updates for TI and ST Microelectronics drivers, and a
> few NCI related changes.
>
> For TI's trf7970a driver:
>
> - Target mode support for trf7970a
> - Suspend/resume support for trf7970a
> - DT properties additions to handle different quirks
> - A bunch of fixes for smartphone IOP related issues
>
> For ST Microelectronics' ST21NFCA and ST21NFCB drivers:
>
> - ISO15693 support for st21nfcb
> - checkpatch and sparse related warning fixes
> - Code cleanups and a few minor fixes
>
> Finally, Marvell added ISO15693 support to the NCI stack, together with a
> couple of NCI fixes.
>
> Thanks in advance for pulling those in.
>
> The following changes since commit 6a5d088a923854569e20eac4f3f569926d5911ec:
>
> carl9170: tx: Replace rcu_assign_pointer() with RCU_INIT_POINTER() (2014-08-28 14:50:13 -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.18-1
>
> for you to fetch changes up to 094e93592433312548dd5e43d7b24b152f658063:
>
> NFC: st21nfca: Fix potential double kfree_skb error (2014-09-24 02:02:24 +0200)
Pulling now, but I don't plan to push it back out until Dave pulls my earlier batch...
--
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-09-26 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 0:34 [GIT] [3.18] NFC update Samuel Ortiz
2014-09-26 17:38 ` 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=20140926173818.GG22967@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.