From: Thorsten Leemhuis <firstname.lastname@example.org>
To: "email@example.com" <firstname.lastname@example.org>
Subject: Re: [PATCH] fix 5.15 init regression for Intel Bluetooth #forregzbot
Date: Tue, 28 Dec 2021 14:37:21 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
On 28.12.21 13:52, Thorsten Leemhuis wrote:
> #regzbot dup-of:
Sorry for the noise, this is the mail with the report:
> TWIMC: this mail is primarily send for documentation purposes and for
> regzbot, my Linux kernel regression tracking bot. These mails usually
> contain '#forregzbot' in the subject, to make them easy to spot and filter.
> On 28.12.21 08:20, Thorsten Leemhuis wrote:
>> [TLDR: I'm adding this regression to regzbot, the Linux kernel
>> regression tracking bot; most text you find below is compiled from a few
>> templates paragraphs some of you might have seen already.]
>> On 27.12.21 11:26, Ortwin Glück wrote:
>>> On all 5.15 kernels the Intel Bluetooth no longer works. All was fine in
>>> Apparently the quirk is needed for this device.
>>> vanilla 5.15.5:
>>> Bluetooth: hci0: Reading Intel version command failed (-110)
>>> Bluetooth: hci0: command tx timeout
>>> with patch:
>>> Bluetooth: hci0: Legacy ROM 2.5 revision 1.0 build 3 week 17 2014
>>> Bluetooth: hci0: Intel device is already patched. patch num: 32
>>> Please apply to stable too.
>> Hi, this is your Linux kernel regression tracker speaking.
>> Thanks for the report.
>> Adding the regression mailing list to the list of recipients, as it
>> should be in the loop for all regressions, as explained here:
>> To be sure this issue doesn't fall through the cracks unnoticed, I'm
>> adding it to regzbot, my Linux kernel regression tracking bot:
>> #regzbot ^introduced v5.14..v5.15
>> #regzbot title bluetooth: Intel Bluetooth no longer works
>> #regzbot ignore-activity
>> Reminder: when fixing the issue, please add a 'Link:' tag with the URL
>> to the report (the parent of this mail) using the kernel.org redirector,
>> as explained in 'Documentation/process/submitting-patches.rst'. Regzbot
>> then will automatically mark the regression as resolved once the fix
>> lands in the appropriate tree. For more details about regzbot see footer.
>> Sending this to everyone that got the initial report, to make all aware
>> of the tracking. I also hope that messages like this motivate people to
>> directly get at least the regression mailing list and ideally even
>> regzbot involved when dealing with regressions, as messages like this
>> wouldn't be needed then.
>> Don't worry, I'll send further messages wrt to this regression just to
>> the lists (with a tag in the subject so people can filter them away), as
>> long as they are intended just for regzbot. With a bit of luck no such
>> messages will be needed anyway.
>> Ciao, Thorsten (wearing his 'Linux kernel regression tracker' hat).
>> P.S.: As a Linux kernel regression tracker I'm getting a lot of reports
>> on my table. I can only look briefly into most of them. Unfortunately
>> therefore I sometimes will get things wrong or miss something important.
>> I hope that's not the case here; if you think it is, don't hesitate to
>> tell me about it in a public reply. That's in everyone's interest, as
>> what I wrote above might be misleading to everyone reading this; any
>> suggestion I gave thus might sent someone reading this down the wrong
>> rabbit hole, which none of us wants.
>> BTW, I have no personal interest in this issue, which is tracked using
>> regzbot, my Linux kernel regression tracking bot
>> (https://linux-regtracking.leemhuis.info/regzbot/). I'm only posting
>> this mail to get things rolling again and hence don't need to be CC on
>> all further activities wrt to this regression.
>> Additional information about regzbot:
>> If you want to know more about regzbot, check out its web-interface, the
>> getting start guide, and/or the references documentation:
>> The last two documents will explain how you can interact with regzbot
>> yourself if your want to.
>> Hint for reporters: when reporting a regression it's in your interest to
>> tell #regzbot about it in the report, as that will ensure the regression
>> gets on the radar of regzbot and the regression tracker. That's in your
>> interest, as they will make sure the report won't fall through the
>> cracks unnoticed.
>> Hint for developers: you normally don't need to care about regzbot once
>> it's involved. Fix the issue as you normally would, just remember to
>> include a 'Link:' tag to the report in the commit message, as explained
>> in Documentation/process/submitting-patches.rst
>> That aspect was recently was made more explicit in commit 1f57bd42b77c:
prev parent reply other threads:[~2021-12-28 13:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <firstname.lastname@example.org>
[not found] ` <email@example.com>
2021-12-28 7:20 ` [PATCH] fix 5.15 init regression for Intel Bluetooth Thorsten Leemhuis
2021-12-28 12:52 ` [PATCH] fix 5.15 init regression for Intel Bluetooth #forregzbot Thorsten Leemhuis
2021-12-28 13:37 ` Thorsten Leemhuis [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).