From: "John W. Linville" <linville@tuxdriver.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: Linux Wireless <linux-wireless@vger.kernel.org>,
Linux NFC <linux-nfc@ml01.01.org>
Subject: Re: [GIT] [3.10] NFC fixes
Date: Wed, 22 May 2013 14:27:47 -0400 [thread overview]
Message-ID: <20130522182747.GG2113@tuxdriver.com> (raw)
In-Reply-To: <20130521230711.GD4566@zurbaran>
On Wed, May 22, 2013 at 01:07:11AM +0200, Samuel Ortiz wrote:
> Hi John,
>
> This is the first batch of NFC fixes for 3.10, and it contains:
>
> - 3 fixes for the NFC MEI support:
> * We now depend on the correct Kconfig symbol.
> * We register an MEI event callback whenever we enable an NFC device,
> otherwise we fail to read anything after an enable/disable cycle.
> * We only disable an MEI device from its disable mey_phy_ops,
> preventing useless consecutive disable calls.
>
> - An NFC Makefile cleanup, as I forgot to remove a commented out line when
> moving the LLCP code to the NFC top level directory.
>
> The following changes since commit 6bb4880d9ef30375da4507aeabd6dc261a2c6c2b:
>
> ath9k: fix draining aggregation tid buffers (2013-05-17 14:31:09 -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.10-1
>
> for you to fetch changes up to e3a6b14ceda0207c3405c6266e5177a85c0db044:
>
> NFC: mei: Do not disable MEI devices from their remove routine (2013-05-21 10:48: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.
next prev parent reply other threads:[~2013-05-22 18:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 23:07 [GIT] [3.10] NFC fixes Samuel Ortiz
2013-05-22 18:27 ` John W. Linville [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-06-06 15:20 Samuel Ortiz
2013-06-12 18:22 ` John W. Linville
2013-06-13 9:02 ` Samuel Ortiz
2013-06-13 15:18 ` 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=20130522182747.GG2113@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).