The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
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 13:27:54 +0200	[thread overview]
Message-ID: <ZpUHuugPspWjwu49@hovoldconsulting.com> (raw)
In-Reply-To: <172099001665.1942258.758282869896052475.tglx@xen13>

On Sun, Jul 14, 2024 at 10:50:06PM +0200, Thomas Gleixner wrote:
> Linus,
> 
> please pull the latest irq/core branch from:
> 
>    git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq-core-2024-07-14
> 
> up to:  faf243d11659: Merge branch 'irq/msi' into irq/core
> 
> Updates for the interrupt subsystem:

>   - MSI
> 
>     - Switch ARM/ARM64 over to the modern per device MSI domains.
> 
>       This simplifies the handling of platform MSI and wire to MSI
>       controllers and removes about 500 lines of legacy code.
> 
>       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:

	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.

Johan

  reply	other threads:[~2024-07-15 11:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-14 20:50 [GIT pull] core/debugobjects for v6.11-rc1 Thomas Gleixner
2024-07-14 20:50 ` [GIT pull] irq/core " Thomas Gleixner
2024-07-15 11:27   ` Johan Hovold [this message]
2024-07-15 12:47     ` Thomas Gleixner
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
  -- strict thread matches above, loose matches on Subject: below --
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=ZpUHuugPspWjwu49@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --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