Re: [PATCH] Bluetooth: btusb: Add support for TP-Link UB500 Adapter

[Marek Vasut <marex@denx.de>]

On 11/16/21 7:35 PM, Greg Kroah-Hartman wrote:
> On Tue, Nov 16, 2021 at 06:41:08PM +0100, Szabolcs Sipos wrote:
>> 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)?
> 
> I will queue it up for the next set of kernels after the current ones are
> released.

btw while you're bringing it up, is there some sure-fire method I can 
use to verify the patch is in Linus tree, besides having a separate 
checkout of that tree ?

I usually have both Linus tree as origin and next in one git tree, so I 
was wondering if there is a recommended way to avoid mistakes like the 
one I made above (and checking at git.kernel.org apparently also has its 
downsides).