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.10] NFC pull request
Date: Mon, 22 Apr 2013 14:55:37 -0400	[thread overview]
Message-ID: <20130422185537.GD2055@tuxdriver.com> (raw)
In-Reply-To: <20130415230508.GL8798@zurbaran>

On Tue, Apr 16, 2013 at 01:05:08AM +0200, Samuel Ortiz wrote:
> Hi John,
> 
> A bit late, but this is the 2nd NFC pull request for 3.10.
> 
> With this one we have:
> 
> - A major pn533 update. The pn533 framing support has been changed in order to
>   easily support all pn533 derivatives. For example we now support the ACR122
>   USB dongle.
> 
> - An NFC MEI physical layer code factorization through the mei_phy NFC API.
>   Both the microread and the pn544 drivers now use it.
> 
> - LLCP aggregation support. This allows NFC p2p devices to send aggregated
>   frames containing all sort of LLCP frames except SYMM and aggregation
>   frames.
> 
> - More LLCP socket options for getting the remote device link parameters.
> 
> - Fixes for the LLCP socket option code added with the first pull request for
>   3.10.
> 
> - Some support for LLCP corner cases like 0 length SDUs and general DISC
>   (tagged with a 0,0 dsap ssap couple) handling.
> 
> - RFKILL support for NFC.
> 
> Thanks in advance for pulling them in.
> 
> The following changes since commit fe29f54cd574eab7b521445419f355c0ecd995cc:
> 
>   ipw2x00: move to kstrto* functions (2013-04-10 14:10:34 -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.10-2
> 
> for you to fetch changes up to bb03dceb83852614ae3ad6b3731a31422890b0b9:
> 
>   NFC: pn544: Add MEI physical layer (2013-04-16 00:39:41 +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:[~2013-04-22 18:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-15 23:05 [GIT] [3.10] NFC pull request Samuel Ortiz
2013-04-22 18:55 ` John W. Linville [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-04-26 23:28 Samuel Ortiz
2013-04-29 19:10 ` John W. Linville
2013-04-26 14:21 Samuel Ortiz
2013-03-11 12:44 Samuel Ortiz
2013-03-08 11:44 Samuel Ortiz

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=20130422185537.GD2055@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).