public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Szabolcs Sipos <labuwx@balfug.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Sasha Levin <sashal@kernel.org>,
	linux-stable <stable@vger.kernel.org>,
	Marek Vasut <marex@denx.de>
Subject: Re: [PATCH] Bluetooth: btusb: Add support for TP-Link UB500 Adapter
Date: Tue, 16 Nov 2021 18:41:08 +0100	[thread overview]
Message-ID: <62685363-e1b3-bc97-431e-a7c8faccb78d@balfug.com> (raw)
In-Reply-To: <YWPrSHGbno3dODKr@kroah.com>

On 10/11/21 09:44, Greg Kroah-Hartman wrote:
> On Sun, Oct 10, 2021 at 10:59:06PM +0200, Marek Vasut wrote:
>> Hello everyone,
>>
>> The following new device USB ID has landed in linux-next recently:
>>
>> 4fd6d4907961 ("Bluetooth: btusb: Add support for TP-Link UB500 Adapter")
>>
>> It would be nice if it could be backported to stable. I verified it works on
>> 5.14.y as a simple cherry-pick .
> 
> A patch needs to be in Linus's tree before we can add it to the stable
> releases.  Please let us know when it gets there and we will be glad to
> pick it up.
> 
> thanks,
> 
> greg k-h

Hello Greg,

The patch has reached Linus's tree:
4fd6d4907961 ("Bluetooth: btusb: Add support for TP-Link UB500 Adapter")

Could you please add it to stable (5.15.y)?

Thanks,
Szabolcs


  reply	other threads:[~2021-11-16 17:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-10 20:59 [PATCH] Bluetooth: btusb: Add support for TP-Link UB500 Adapter Marek Vasut
2021-10-11  7:44 ` Greg Kroah-Hartman
2021-11-16 17:41   ` Szabolcs Sipos [this message]
2021-11-16 18:35     ` Greg Kroah-Hartman
2021-11-16 19:58       ` Marek Vasut
2021-11-17  6:35         ` Greg Kroah-Hartman
2021-11-17 20:27           ` Marek Vasut
2021-11-18  8:23             ` Greg Kroah-Hartman
2021-11-18 10:19               ` Marek Vasut

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=62685363-e1b3-bc97-431e-a7c8faccb78d@balfug.com \
    --to=labuwx@balfug.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=marex@denx.de \
    --cc=sashal@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