From: Thomas Gleixner <tglx@linutronix.de>
To: Johan Hovold <johan@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [GIT pull] irq/core for v6.11-rc1
Date: Mon, 15 Jul 2024 14:47:31 +0200 [thread overview]
Message-ID: <87o76yrfdo.ffs@tglx> (raw)
In-Reply-To: <ZpUHuugPspWjwu49@hovoldconsulting.com>
On Mon, Jul 15 2024 at 13:27, Johan Hovold wrote:
> On Sun, Jul 14, 2024 at 10:50:06PM +0200, Thomas Gleixner wrote:
>> Aside of that it paves the way for ARM/ARM64 to utilize the dynamic
>> allocation of PCI/MSI interrupts and to support the upcoming non
>> standard IMS (Interrupt Message Store) mechanism on PCIe devices
>
> This only showed up in linux-next last Friday and broke PCI/MSI
> interrupts on Qualcomm machines like the Lenovo ThinkPad X13s as I just
> reported here:
Bah. It got late into next because we asked people for weeks to test it...
> https://lore.kernel.org/all/ZpUFl4uMCT8YwkUE@hovoldconsulting.com/
>
> I have not had time to debug this further, but it may be worth holding
> off on merging until we've taken a closer at look at the breakage.
Yes. Linus please ignore that branch for now.
Thanks,
tglx
next prev parent reply other threads:[~2024-07-15 12:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-14 20:50 [GIT pull] core/debugobjects " Thomas Gleixner
2024-07-14 20:50 ` [GIT pull] irq/core " Thomas Gleixner
2024-07-15 11:27 ` Johan Hovold
2024-07-15 12:47 ` Thomas Gleixner [this message]
2024-07-14 20:50 ` [GIT pull] smp/core " Thomas Gleixner
2024-07-15 23:56 ` pr-tracker-bot
2024-07-14 20:50 ` [GIT pull] timers/core " Thomas Gleixner
2024-07-15 23:56 ` pr-tracker-bot
2024-07-15 23:56 ` [GIT pull] core/debugobjects " pr-tracker-bot
2024-07-22 19:27 [GIT pull] irq/core " Thomas Gleixner
2024-07-22 21:09 ` pr-tracker-bot
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=87o76yrfdo.ffs@tglx \
--to=tglx@linutronix.de \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@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
all inboxes | Powered by JetHome®