public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
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 14:26:56 +0000	[thread overview]
Message-ID: <2023113024-huff-cushy-3b6b@gregkh> (raw)
In-Reply-To: <tencent_7B1A767250D25DDD0AA40C93@qq.com>

On Thu, Nov 30, 2023 at 10:17:16PM +0800, 关文涛 wrote:
> > Can you provide just a list of git ids, without footnotes or links, as
> > that is a pain to attempt to cut-paste from?
> Sure,
> 
> v5.15 git id list:
> 18e8055c88142d8f6e23ebdc38c126ec37844e5d
> 8b1d66b50437b65ef109f32270bd936ca5437a83
> 
> v5.10 git id list:
> 0d484db60fc0c5f8848939a61004c6fa01fad61a
> 18e8055c88142d8f6e23ebdc38c126ec37844e5d
> 8b1d66b50437b65ef109f32270bd936ca5437a83
> 
> v5.4 git id list:
> 0d484db60fc0c5f8848939a61004c6fa01fad61a
> 18e8055c88142d8f6e23ebdc38c126ec37844e5d
> 8b1d66b50437b65ef109f32270bd936ca5437a83

These do not apply cleanly to those kernel trees, can you please provide
a working set of backported patches that are fixed up and tested for
these branches?

thanks,

greg k-h

  reply	other threads:[~2023-11-30 14:26 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
2023-11-30 14:17           ` 关文涛
2023-11-30 14:26             ` Greg KH [this message]
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=2023113024-huff-cushy-3b6b@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