From: "bumyong.lee" <bumyong.lee@samsung.com>
To: "'Linux regressions mailing list'" <regressions@lists.linux.dev>,
"'karthikeyan'" <karthikeyan@linumiz.com>, <vkoul@kernel.org>
Cc: <dmaengine@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<parthiban@linumiz.com>, <saravanan@linumiz.com>
Subject: RE: dmaengine: CPU stalls while loading bluetooth module
Date: Fri, 8 Mar 2024 19:07:23 +0900 [thread overview]
Message-ID: <000001da7140$6a0f1570$3e2d4050$@samsung.com> (raw)
In-Reply-To: <12de921e-ae42-4eb3-a61a-dadc6cd640b8@leemhuis.info>
Hello
> Hmmm. 6.8 final is due. Is that something we can live with? Or would it be
> a good idea to revert above commit for now and reapply it when something
> better emerged? I doubt that the answer is "yes, let's do that", but I
> have to ask.
I couldn't find better way now.
I think it's better to follow you mentioned
>
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> --
> Everything you wanna know about Linux kernel regression tracking:
> https://protect2.fireeye.com/v1/url?k=1721f6f7-48bacfe8-17207db8-
> 000babdfecba-6a9835eff37b0303&q=1&e=f39e15ee-403b-4efb-a56e-
> f6aba3905bc5&u=https%3A%2F%2Flinux-
> regtracking.leemhuis.info%2Fabout%2F%23tldr
> If I did something stupid, please tell me, as explained on that page.
>
> P.S.: To be sure the issue doesn't fall through the cracks unnoticed, I'm
> adding it to regzbot, the Linux kernel regression tracking bot:
>
> #regzbot report /
> #regzbot introduced 22a9d9585812440211b
> #regzbot duplicate: https://lore.kernel.org/lkml/ZYhQ2-OnjDgoqjvt@wens.tw/
> #regzbot title dmaengine: CPU stalls while loading bluetooth module
> #regzbot ignore-activity
next prev parent reply other threads:[~2024-03-08 10:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240305062038epcas2p143c5e1e725d8a934b0208266a2f78ccb@epcas2p1.samsung.com>
2024-03-05 6:20 ` dmaengine: CPU stalls while loading bluetooth module karthikeyan
2024-03-05 7:13 ` bumyong.lee
2024-03-08 8:51 ` Linux regression tracking (Thorsten Leemhuis)
2024-03-08 10:07 ` bumyong.lee [this message]
2024-03-19 9:07 ` Linux regression tracking (Thorsten Leemhuis)
2024-03-20 0:49 ` bumyong.lee
2024-03-20 6:28 ` Linux regression tracking (Thorsten Leemhuis)
2024-03-26 13:50 ` Linux regression tracking (Thorsten Leemhuis)
2024-03-28 6:51 ` Vinod Koul
2024-03-28 15:06 ` Linux regression tracking (Thorsten Leemhuis)
2024-04-25 10:03 ` Thorsten Leemhuis
2024-04-29 4:49 ` Vinod Koul
2024-04-29 4:58 ` Linux regression tracking (Thorsten Leemhuis)
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='000001da7140$6a0f1570$3e2d4050$@samsung.com' \
--to=bumyong.lee@samsung.com \
--cc=dmaengine@vger.kernel.org \
--cc=karthikeyan@linumiz.com \
--cc=linux-kernel@vger.kernel.org \
--cc=parthiban@linumiz.com \
--cc=regressions@lists.linux.dev \
--cc=saravanan@linumiz.com \
--cc=vkoul@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