From: Greg KH <gregkh@linuxfoundation.org>
To: 关文涛 <guanwentao@uniontech.com>
Cc: stable <stable@vger.kernel.org>, Sasha Levin <sashal@kernel.org>,
hildawu <hildawu@realtek.com>
Subject: Re: [Re V2]:Patch "Bluetooth: btusb: Add 0bda:b85b for Fn-Link RTL8852BE" has been added to the 5.10-stable tree
Date: Thu, 30 Nov 2023 13:30:25 +0000 [thread overview]
Message-ID: <2023113015-justifier-nastiness-3c66@gregkh> (raw)
In-Reply-To: <tencent_429FA9BD3B6671BC788386A6@qq.com>
On Sat, Nov 25, 2023 at 12:56:34AM +0800, 关文涛 wrote:
> Hello Greg:
> I thiink that the most clean thing that backport to v6.1 lts tree,
> because it has "Add support for RTL8852B" commit link [1]:
>
> In v5.15 lts tree,it miss patch [1].
> In v5.10 lts tree,it miss "Add support for RTL8852A"[2] so "git am"
> command not simply work,but without the patch RTL8852B works.
> In v5.4 lts tree,it miss more ids,need more efforts to do.If someone
> need,need to backport their own pid/vid pairs.
> In v4.19 lts tree,it miss patch [3],so firmware download will failed.
>
> For backport patches[4][5][6][7][8],
> they miss "Add support for RTL8852C"[9] in v5.15 and v5.10 lts tree.
> Otherwise,I also found that in v5.10 lts tree path file:
> root/drivers/bluetooth/btusb.c
> MT7922 id [10] [11] add without its dependency [12] [13]
> AX210 id [14] add without its dependency [15]
> Sorry for maybe I miss some device id.How do other people think the
> situation where some BT ids backports are done without dependencies?
Can you provide just a list of git ids, without footnotes or links, as
that is a pain to attempt to cut-paste from?
Better yet, can you provide backported patch series of the needed
commits like is sent all the time to the stable mailing list (so you can
see examples) and we can take them that way? That way you get credit
for the backporting and testing as you will have added your
signed-off-by to the commits.
thanks,
greg k-h
next prev parent reply other threads:[~2023-11-30 13:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231124043548.86153-1-sashal@kernel.org>
[not found] ` <tencent_27789A681229CCB77BE3E186@qq.com>
2023-11-24 14:59 ` [Re V2]:Patch "Bluetooth: btusb: Add 0bda:b85b for Fn-Link RTL8852BE" has been added to the 5.10-stable tree 关文涛
2023-11-24 15:12 ` Greg KH
2023-11-24 16:56 ` 关文涛
2023-11-30 13:30 ` Greg KH [this message]
2023-11-30 14:17 ` 关文涛
2023-11-30 14:26 ` Greg KH
2023-11-30 14:45 ` 关文涛
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=2023113015-justifier-nastiness-3c66@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=guanwentao@uniontech.com \
--cc=hildawu@realtek.com \
--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