From: Greg KH <gregkh@linuxfoundation.org>
To: incogcyberpunk@proton.me
Cc: Doug Anderson <dianders@chromium.org>,
Thorsten Leemhuis <regressions@leemhuis.info>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"marcel@holtmann.org" <marcel@holtmann.org>,
"luiz.dentz@gmail.com" <luiz.dentz@gmail.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"johan.hedberg@gmail.com" <johan.hedberg@gmail.com>,
"sean.wang@mediatek.com" <sean.wang@mediatek.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION] Bluetooth adapter provided by `btusb` not recognized since v6.13.2
Date: Thu, 20 Nov 2025 17:43:21 +0100 [thread overview]
Message-ID: <2025112001-omen-idealness-19d4@gregkh> (raw)
In-Reply-To: <dA269ZfA6vvmePZBF3DBULVIDsK_zAWujzWKpPy44BQ0QGB6t6pG5JVTt8lwsArauLABj3oMiZVMEzM8GzjJKgx1iqQNwkICiGq9cNtaZak=@proton.me>
On Thu, Nov 20, 2025 at 04:35:27PM +0000, incogcyberpunk@proton.me wrote:
> So, now does this patch for the regression gets merged upstream for the next mainline and stable releases ?
Please read:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
for how this happens.
prev parent reply other threads:[~2025-11-20 16:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 1:30 [REGRESSION] Bluetooth adapter provided by `btusb` not recognized since v6.13.2 incogcyberpunk
2025-11-17 9:42 ` Thorsten Leemhuis
2025-11-17 10:55 ` Thorsten Leemhuis
2025-11-17 16:48 ` Thorsten Leemhuis
2025-11-17 17:20 ` Doug Anderson
2025-11-19 8:05 ` incogcyberpunk
2025-11-19 16:55 ` Doug Anderson
2025-11-20 0:43 ` incogcyberpunk
2025-11-20 0:53 ` Doug Anderson
2025-11-20 1:03 ` incogcyberpunk
2025-11-20 6:30 ` Doug Anderson
2025-11-20 10:14 ` incogcyberpunk
2025-11-20 16:03 ` Doug Anderson
2025-11-20 16:35 ` incogcyberpunk
2025-11-20 16:43 ` Greg KH [this message]
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=2025112001-omen-idealness-19d4@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=dianders@chromium.org \
--cc=incogcyberpunk@proton.me \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=sean.wang@mediatek.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.