dmaengine.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Vinod Koul <vkoul@kernel.org>,
	Linux regressions mailing list <regressions@lists.linux.dev>
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
	parthiban@linumiz.com, saravanan@linumiz.com,
	'karthikeyan' <karthikeyan@linumiz.com>,
	"bumyong.lee" <bumyong.lee@samsung.com>
Subject: Re: dmaengine: CPU stalls while loading bluetooth module
Date: Thu, 25 Apr 2024 12:03:29 +0200	[thread overview]
Message-ID: <0b5da67a-7482-4f18-9246-9c118f182b8b@leemhuis.info> (raw)
In-Reply-To: <2b2a6c9f-4df2-4962-b926-09adccd20715@leemhuis.info>

On 28.03.24 16:06, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 28.03.24 07:51, Vinod Koul wrote:
>> On 26-03-24, 14:50, Linux regression tracking (Thorsten Leemhuis) wrote:
>>>
>>> Vinod Koul, what's your option here? We have two reports about
>>> regressions caused by 22a9d958581244 ("dmaengine: pl330: issue_pending
>>> waits until WFP state") [v6.8-rc1] now:
>>>
>>> https://lore.kernel.org/lkml/1553a526-6f28-4a68-88a8-f35bd22d9894@linumiz.com/
>>>
>>> https://lore.kernel.org/all/ZYhQ2-OnjDgoqjvt@wens.tw/
>>> [the first link points to the start of this thread]
>>>
>>> To me it sounds like this is a change that better should be reverted,
>>> but you are of course the better judge here.
>>
>> Sure I have reverted this,
>
> Thx!

That revert afaics has not made it to Linus yet. Is that intentional, or
did it just fell through the cracks?

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.

#regzbot poke

  reply	other threads:[~2024-04-25 10:03 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
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 [this message]
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=0b5da67a-7482-4f18-9246-9c118f182b8b@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=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;
as well as URLs for NNTP newsgroup(s).