linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Ortiz <sameo@linux.intel.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Linux NFC <linux-nfc@lists.01.org>,
	Linux Wireless <linux-wireless@vger.kernel.org>
Subject: [GIT] [3.10] NFC pull request
Date: Mon, 11 Mar 2013 13:44:47 +0100	[thread overview]
Message-ID: <20130311124447.GA2164@zurbaran> (raw)

Hi John,

This is the first NFC pull request for the 3.10 kernel. I have now rebased
those changes on top of wireless-next and they build fine.

The 2 features we have with this one are:

- An LLCP Service Name Lookup (SNL) netlink interface for querying LLCP
  service availability from user space.
  Along the way, Thierry also improved the existing SNL interface for
  aggregating SNL responses.

- An initial LLCP socket options implementation, for setting the Receive
  Window (RW) and the Maximum Information Unit Extension (MIUX) per socket.
  This is need for the LLCP validation tests.

We also have a microread MEI build failure here: I am not sending this one to
3.9 because the MEI bus code is not there yet, so it won't break for anyone
else than me.

Thanks in advance for pulling them in.

The following changes since commit c678fb2a915b71f8faa78d9ab6d409b8ff3276cc:

  mwifiex: fix potential null dereference 'mef_entry' (2013-03-08 16:02:48 -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.10-1

for you to fetch changes up to 40213fa8513c2a92e7390f25571f7c17c7955e2b:

  NFC: llcp: Add cleanup support for unreplied SNL requests (2013-03-10 23:16:41 +0100)

----------------------------------------------------------------
Samuel Ortiz (5):
      NFC: microread: Fix MEI build failure
      NFC: llcp: Rename socket rw and miu fields
      NFC: llcp: Implement socket options
      NFC: llcp: Use socket specific link parameters before the local ones
      NFC: llcp: Remove redundant printk

Thierry Escande (4):
      NFC: Add missing type policies for netlink attributes
      NFC: llcp: Service Name Lookup SDRES aggregation
      NFC: llcp: Service Name Lookup netlink interface
      NFC: llcp: Add cleanup support for unreplied SNL requests

 drivers/nfc/microread/mei.c |    2 +-
 include/linux/socket.h      |    1 +
 include/uapi/linux/nfc.h    |   16 ++++
 net/nfc/llcp/commands.c     |  205 +++++++++++++++++++++++++++++++++++--------
 net/nfc/llcp/llcp.c         |  112 ++++++++++++++++++++---
 net/nfc/llcp/llcp.h         |   36 +++++++-
 net/nfc/llcp/sock.c         |  130 +++++++++++++++++++++++++--
 net/nfc/netlink.c           |  172 ++++++++++++++++++++++++++++++++++++
 net/nfc/nfc.h               |   14 +++
 9 files changed, 634 insertions(+), 54 deletions(-)
-- 
Intel Open Source Technology Centre
http://oss.intel.com/

             reply	other threads:[~2013-03-11 12:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-11 12:44 Samuel Ortiz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-04-26 23:28 [GIT] [3.10] NFC pull request Samuel Ortiz
2013-04-29 19:10 ` John W. Linville
2013-04-26 14:21 Samuel Ortiz
2013-04-15 23:05 Samuel Ortiz
2013-04-22 18:55 ` John W. Linville
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=20130311124447.GA2164@zurbaran \
    --to=sameo@linux.intel.com \
    --cc=linux-nfc@lists.01.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).