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.9] NFC fixes
Date: Mon, 1 Apr 2013 15:15:51 -0400 [thread overview]
Message-ID: <20130401191550.GC3526@tuxdriver.com> (raw)
In-Reply-To: <20130331232610.GQ2153@zurbaran>
On Mon, Apr 01, 2013 at 01:26:10AM +0200, Samuel Ortiz wrote:
> Hi John,
>
> This is the 2nd batch of NFC fixes for 3.9. This time we have:
>
> - A crash fix for when a DGRAM LLCP socket is listening while the NFC adapter
> is physically removed.
> - A potential double skb free when the LLCP socket receive queue is full.
> - A fix for properly handling multiple and consecutive LLCP connections, and
> not trash the socket ack log.
> - A build failure for the MEI microread physical layer, now that the MEI bus
> APIs have been merged into char-misc-next.
>
> The following changes since commit 36ef0b473fbf43d5db23eea4616cc1d18cec245f:
>
> rtlwifi: usb: add missing freeing of skbuff (2013-03-18 15:20:38 -0400)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/sameo/nfc-fixes.git tags/nfc-fixes-3.9-2
>
> for you to fetch changes up to 9593b0b1179c526436f14849a9587fd2aae12040:
>
> NFC: microread: Fix build failure due to a new MEI bus API (2013-04-01 00:52:42 +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.
next prev parent reply other threads:[~2013-04-01 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-31 23:26 [GIT] [3.9] NFC fixes Samuel Ortiz
2013-04-01 19:15 ` John W. Linville [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-03-10 23:57 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=20130401191550.GC3526@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).