public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Salvatore Bonaccorso <carnil@debian.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Trent Piepho <tpiepho@gmail.com>, stable <stable@vger.kernel.org>,
	Sasha Levin <sashal@kernel.org>,
	Marcel Holtmann <marcel@holtmann.org>
Subject: Re: Please apply commit 517b693351a2 ("Bluetooth: btusb: Always fallback to alt 1 for WBS") to back to v5.10.y
Date: Sun, 21 Feb 2021 14:17:41 +0100	[thread overview]
Message-ID: <YDJddZykdgO5kShh@eldamar.lan> (raw)
In-Reply-To: <YDJcMQnGWTIFG7k5@kroah.com>

Hi Greg,

On Sun, Feb 21, 2021 at 02:12:17PM +0100, Greg Kroah-Hartman wrote:
> On Sun, Feb 21, 2021 at 05:03:34AM -0800, Trent Piepho wrote:
> > On Sun, Feb 21, 2021 at 4:53 AM Greg Kroah-Hartman
> > <gregkh@linuxfoundation.org> wrote:
> > > On Sun, Feb 21, 2021 at 01:46:10PM +0100, Salvatore Bonaccorso wrote:
> > > > Hi
> > > >
> > > > 517b693351a2 ("Bluetooth: btusb: Always fallback to alt 1 for WBS")
> > > > was applied to mainline fixing (restoring) behaviour to pre 5.7. As
> > > > the commit message describes in effect, WBS was broken for all USB-BT
> > > > adapters that do not support alt 6.
> > > >
> > > > Can you consider it to apply it to back to 5.10.y?
> > >
> > > I do not see any such git commit id in Linus's tree, are you sure you
> > > picked the right one?
> > 
> > Full hash is 517b693351a2d04f3af1fc0e506ac7e1346094de.
> > 
> > Looks like it should work as I intended on current 5.10.y, but I
> > didn't test that kernel.
> 
> Ah, this thing isn't even in 5.11, it just now showed up in Linus's
> tree.
> 
> Give it time to hit at least a released version (i.e. 5.12-rc1) before
> we pull it into a stable release.  Unless the bluetooth maintainers say
> it is ok to do so earlier than that.

Sure. We got a request in Debian to include the commit for an upcoming
5.10.y based update and just want to make sure we do not diverge here
from upstream.  But it's obviously good to wait then unless bluetooth
maintainers give the ack earlier.

Thanks for the quick responses.

Regards,
Salvatore

  reply	other threads:[~2021-02-21 13:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-21 12:46 Please apply commit 517b693351a2 ("Bluetooth: btusb: Always fallback to alt 1 for WBS") to back to v5.10.y Salvatore Bonaccorso
2021-02-21 12:53 ` Greg Kroah-Hartman
2021-02-21 13:03   ` Trent Piepho
2021-02-21 13:12     ` Greg Kroah-Hartman
2021-02-21 13:17       ` Salvatore Bonaccorso [this message]
2021-02-22 10:12         ` Greg Kroah-Hartman
2021-02-21 13:30     ` Sjoerd Simons

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=YDJddZykdgO5kShh@eldamar.lan \
    --to=carnil@debian.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=marcel@holtmann.org \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=tpiepho@gmail.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