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.12] NFC fix
Date: Mon, 6 Jan 2014 14:22:42 -0500 [thread overview]
Message-ID: <20140106192242.GE10885@tuxdriver.com> (raw)
In-Reply-To: <20140104234802.GA10578@zurbaran>
3.13 is the current stream. Do you want to adjust your tag name?
John
On Sun, Jan 05, 2014 at 12:48:02AM +0100, Samuel Ortiz wrote:
> Hi John,
>
> Hopefully it's not too late for a 3.12 fix for NFC. Please let me know
> if it is, and I'll add it to my 3.13 pull request.
>
> This pull request only contains one fix for a regression introduced with
> commit e29a9e2ae165620d. Without this fix, we can not establish a p2p link
> in target mode. Only initiator mode works.
>
> The following changes since commit b7e047358449f8eb5cba8197b42280b676b82e54:
>
> Merge branch 'for-upstream' of git://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth (2013-12-18 13:46:08 -0500)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/sameo/nfc-fixes.git tags/nfc-fixes-3.12-1
>
> for you to fetch changes up to d31652a26bc9e752a99b6ac3b61353129934e451:
>
> NFC: Fix target mode p2p link establishment (2014-01-04 03:31:32 +0100)
>
> ----------------------------------------------------------------
> Arron Wang (1):
> NFC: Fix target mode p2p link establishment
>
> net/nfc/core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --
> Intel Open Source Technology Centre
> http://oss.intel.com/
>
--
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:[~2014-01-06 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-04 23:48 [GIT] [3.12] NFC fix Samuel Ortiz
2014-01-06 19:22 ` John W. Linville [this message]
2014-01-06 20:09 ` Samuel Ortiz
2014-01-08 18:38 ` 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=20140106192242.GE10885@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.