From: Greg KH <gregkh@linuxfoundation.org>
To: 关文涛 <guanwentao@uniontech.com>
Cc: Sasha Levin <sashal@kernel.org>,
stable-commits <stable-commits@vger.kernel.org>,
stable <stable@vger.kernel.org>, marcel <marcel@holtmann.org>,
"luiz.dentz" <luiz.dentz@gmail.com>,
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: Fri, 24 Nov 2023 15:12:09 +0000 [thread overview]
Message-ID: <2023112442-glitzy-rocking-4a8a@gregkh> (raw)
In-Reply-To: <tencent_13CC3606408C86A21D09FB05@qq.com>
On Fri, Nov 24, 2023 at 02:59:15PM +0000, 关文涛 wrote:
> Hello Levin:
>
> Apologize for my HTML format past.I discovered that the backport patches also have dependency in 5.10 lts tree:
>
> [1]https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.10.201&id=75742ffc3630203e95844c72c7144f507e2a557d
> [2]https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.10.201&id=40e2e7f1bf0301d1ed7437b10d9e1c92cb51bf81
> [3]https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.10.201&id=9c45bb363e26e86ebaf20f6d2009bedf19fc0d39
> [4]https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.10.201&id=3a292cb18132cb7af3a146613f1c9a47ef6f8463
> [5]https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.10.201&id=1a2a2e34569cf85cad743ee8095d07c3cba5473b
>
> and update version 2 depend patches link:
>
> [1] RTL8852AE: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0d484db60fc0c5f8848939a61004c6fa01fad61a
> [2] RTL8852BE: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=18e8055c88142d8f6e23ebdc38c126ec37844e5d
> [3] RTL8852CE: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8b1d66b50437b65ef109f32270bd936ca5437a83
> [4] FW: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cf0d9a705d81a0f581865cefe0880f29589dd06f
I'm sorry, but I do not understand what we need to do here.
What git ids need to go to what tree and in what order?
> I would like to express my gratitude for you efforts,and I want to provide you with the backport tip when kernel <=5.10 :
> the RTL8852{A,B,C} BT chip series depend patches in that patch [1](v5.11) and load new firmware need that patch [2](v5.4).
> Apologize for my pool English.
Your english is great, but I really don't understand what is to be done
here. Can you just list the ids in the order which you want them
applied and to what tree(s)?
thanks,
greg k-h
next prev parent reply other threads:[~2023-11-24 15:12 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 [this message]
2023-11-24 16:56 ` 关文涛
2023-11-30 13:30 ` Greg KH
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=2023112442-glitzy-rocking-4a8a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=guanwentao@uniontech.com \
--cc=hildawu@realtek.com \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=sashal@kernel.org \
--cc=stable-commits@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