From: Jonathan Nieder <jrnieder@gmail.com>
To: stable@vger.kernel.org
Cc: linux-bluetooth@vger.kernel.org, "Cho, Yu-Chen" <acho@novell.com>,
Henry-Nicolas Tourneur <henry.nicolas@tourneur.be>,
Marcel Holtmann <marcel@holtmann.org>,
Gustavo Padovan <gustavo@padovan.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Oliver Neukum <oliver@neukum.name>,
"Lee, Chun-Yi" <jlee@suse.com>,
Greg KH <gregkh@linux-foundation.org>
Subject: [3.0.y, 3.2.y, 3.3.y] Re: [PATCH] Add Atheros maryann PIDVID support
Date: Thu, 12 Apr 2012 16:58:20 -0500 [thread overview]
Message-ID: <20120412215819.GA15416@burratino> (raw)
In-Reply-To: <00c20c839b7ac6f027ab935f8cf0992c93c5f2fd.1329809368.git.acho@suse.com>
Hi Greg,
Please consider
9498ba7a1d38 Bluetooth: Adding USB device 13d3:3375 as an Atheros AR3012
07c0ea874d43 Bluetooth: Add Atheros maryann PIDVID support
for application to the 3.0.y, 3.2.y, and 3.3.y stable trees. These
add additional USB IDs to the list recognized by the ath3k firmware
loader.
Henry-Nicolas Tourneur wrote[1]:
> I did just complete a test using a 3.0.25 and it's working with the
> patched kernel.
> rfkill switches are working and pairing is working too :)
>
> All done using Wheezy bluetooth stack with gnome tools.
so the second of the two patches is
Tested-by: Henry-Nicolas Tourneur <henry.nicolas@tourneur.be>
Both patches have been in linux-next for a while. The first reached
Linus's master a few weeks ago and the second hit master today.
Thanks,
Jonathan
[1] http://bugs.debian.org/664726
next prev parent reply other threads:[~2012-04-12 21:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 11:09 [PATCH] Add Atheros maryann PIDVID support acho
2012-02-21 11:16 ` Marcel Holtmann
2012-03-16 15:24 ` Johan Hedberg
2012-03-28 21:36 ` Jonathan Nieder
2012-03-30 10:09 ` Johan Hedberg
2012-04-12 21:58 ` Jonathan Nieder [this message]
2012-04-19 19:46 ` [3.0.y, 3.2.y, 3.3.y] " Greg KH
2012-04-19 20:52 ` Jonathan Nieder
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=20120412215819.GA15416@burratino \
--to=jrnieder@gmail.com \
--cc=acho@novell.com \
--cc=gregkh@linux-foundation.org \
--cc=gustavo@padovan.org \
--cc=henry.nicolas@tourneur.be \
--cc=jlee@suse.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=oliver@neukum.name \
--cc=stable@vger.kernel.org \
/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.