linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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.16] NFC update
Date: Fri, 30 May 2014 13:42:59 -0400	[thread overview]
Message-ID: <20140530174259.GF24054@tuxdriver.com> (raw)
In-Reply-To: <20140529232016.GA19965@zurbaran>

On Fri, May 30, 2014 at 01:20:16AM +0200, Samuel Ortiz wrote:
> Hi John,
> 
> Hopefully not too late for a last NFC pull request for 3.16.
> We have:
> 
> - Felica (Type3) tags support for trf7970a
> - Type 4b tags support for port100
> - st21nfca DTS typo fix
> - A few sparse warning fixes
> 
> Thanks in advance for pulling them in.
> 
> The following changes since commit ef1b075c15d55c71200c63450756a9bb51ce2a60:
> 
>   mwifiex: use 'const' qualifier for 2nd arg of mwifiex_tdls_add_ht_oper (2014-05-22 14:21:12 -0400)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/sameo/nfc-next.git nfc-next-3.16-2
> 
> for you to fetch changes up to 6857bb96271cd40ffb38825d43897d716310e3db:
> 
>   NFC: trf7970a: Add support for Felica Type 3 tags (2014-05-26 01:28:28 +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.

  reply	other threads:[~2014-05-30 18:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-29 23:20 [GIT] [3.16] NFC update Samuel Ortiz
2014-05-30 17:42 ` John W. Linville [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-05-20 22:13 Samuel Ortiz
2014-05-22 17:57 ` John W. Linville

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=20140530174259.GF24054@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).