From: Greg KH <greg@kroah.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: AceLan Kao <acelan.kao@canonical.com>,
stable@vger.kernel.org, linux-bluetooth@vger.kernel.org
Subject: Re: [3.0,3.2][PATCH] Bluetooth: Add support for Atheros [04ca:3005]
Date: Tue, 24 Apr 2012 10:47:16 -0700 [thread overview]
Message-ID: <20120424174716.GB28788@kroah.com> (raw)
In-Reply-To: <20120424035114.GA30442@burratino>
On Mon, Apr 23, 2012 at 10:51:14PM -0500, Jonathan Nieder wrote:
> AceLan Kao wrote:
>
> > [Subject: [3.0,3.2][PATCH] Bluetooth: Add support for Atheros [04ca:3005]]
> >
> > commit 55ed7d4d1469eafbe3ad7e8fcd44f5af27845a81 upstream
>
> Looks reasonable. Should 3.3.y get this, too?
Yes, AceLan, please don't think you can skip stable kernel trees, all
that are relevant should have the patches applied.
greg k-h
prev parent reply other threads:[~2012-04-24 17:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1335237105-12291-1-git-send-email-acelan.kao@canonical.com>
2012-04-24 3:51 ` [3.0,3.2][PATCH] Bluetooth: Add support for Atheros [04ca:3005] Jonathan Nieder
2012-04-24 17:47 ` Greg KH [this message]
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=20120424174716.GB28788@kroah.com \
--to=greg@kroah.com \
--cc=acelan.kao@canonical.com \
--cc=jrnieder@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox