From: Samuel Ortiz <sameo@linux.intel.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Linux Wireless <linux-wireless@vger.kernel.org>,
Linux NFC <linux-nfc@lists.01.org>
Subject: [GIT] [3.14] NFC fix
Date: Sun, 23 Feb 2014 23:50:54 +0100 [thread overview]
Message-ID: <20140223225054.GN18868@zurbaran> (raw)
Hi John,
We only have one candidate for 3.14 fixes, and this is a NCI NULL
pointer dereference introduced during the 3.14 merge window.
The following changes since commit b3050248c167871ca52cfdb2ce78aa2460249346:
ath9k: Fix ETSI compliance for AR9462 2.0 (2014-02-20 15:53:20 -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.14-1
for you to fetch changes up to 44a589ca2de4d7980f8b335481a09bf818065dbe:
NFC: NCI: Fix NULL pointer dereference (2014-02-23 23:14:45 +0100)
Amitkumar Karwar (1):
NFC: NCI: Fix NULL pointer dereference
net/nfc/nci/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
Intel Open Source Technology Centre
http://oss.intel.com/
next reply other threads:[~2014-02-23 22:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 22:50 Samuel Ortiz [this message]
2014-02-24 19:44 ` [GIT] [3.14] NFC fix 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=20140223225054.GN18868@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).