From: Thomas Gleixner <tglx@linutronix.de>
To: Alexey Klimov <alexey.klimov@linaro.org>, linux-next@vger.kernel.org
Cc: peterz@infradead.org, neil.armstrong@linaro.org,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
andersson@kernel.org, mathieu.poirier@linaro.org
Subject: Re: [linux-next regression] remoteproc seems to be broken
Date: Mon, 12 May 2025 21:05:43 +0200 [thread overview]
Message-ID: <87tt5pk5tk.ffs@tglx> (raw)
In-Reply-To: <D9SXI3F82EFT.7WY8FQ9P4RHL@linaro.org>
On Sun, May 11 2025 at 02:09, Alexey Klimov wrote:
> Hi,
>
> we started to observe regression on linux-next starting with next-20250508.
> Neil bisected it and it pointed to:
> 2ef2e13094c7510c40833951c2ec36cf8574331a
> genirq/chip: Rework handle_nested_irq()
> https://lore.kernel.org/all/20250429065420.744042890@linutronix.de
>
>>No functional change.
>
> Manually reverting that commit resolved the problem for me.
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=irq/core
prev parent reply other threads:[~2025-05-12 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-11 1:09 [linux-next regression] remoteproc seems to be broken Alexey Klimov
2025-05-12 19:05 ` Thomas Gleixner [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=87tt5pk5tk.ffs@tglx \
--to=tglx@linutronix.de \
--cc=alexey.klimov@linaro.org \
--cc=andersson@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=neil.armstrong@linaro.org \
--cc=peterz@infradead.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