From: Borislav Petkov <bp@alien8.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] irq/urgent for v6.8-rc5
Date: Sun, 18 Feb 2024 11:38:37 +0100 [thread overview]
Message-ID: <20240218103837.GAZdHeLbPN7pXCkE3L@fat_crate.local> (raw)
Hi Linus,
please pull a bunch of irqchip fixes for v6.8-rc5.
Thx.
---
The following changes since commit 841c35169323cd833294798e58b9bf63fa4fa1de:
Linux 6.8-rc4 (2024-02-11 12:18:13 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq_urgent_for_v6.8_rc5
for you to fetch changes up to af9acbfc2c4b72c378d0b9a2ee023ed01055d3e2:
irqchip/gic-v3-its: Fix GICv4.1 VPE affinity update (2024-02-13 11:29:52 +0100)
----------------------------------------------------------------
- Fix GICv4.1 affinity update
- Restore a quirk for ACPI-based GICv4 systems
- Handle non-coherent GICv4 redistributors properly
- Prevent spurious interrupts on Broadcom devices using GIC v3
architecture
- Other minor fixes
----------------------------------------------------------------
Bibo Mao (1):
irqchip/loongson-eiointc: Use correct struct type in eiointc_domain_alloc()
Dan Carpenter (1):
irqchip/qcom-mpm: Fix IS_ERR() vs NULL check in qcom_mpm_init()
Doug Berger (1):
irqchip/irq-brcmstb-l2: Add write memory barrier before exit
Marc Zyngier (3):
irqchip/gic-v3-its: Handle non-coherent GICv4 redistributors
irqchip/gic-v3-its: Restore quirk probing for ACPI-based systems
irqchip/gic-v3-its: Fix GICv4.1 VPE affinity update
drivers/irqchip/irq-brcmstb-l2.c | 5 ++-
drivers/irqchip/irq-gic-v3-its.c | 62 ++++++++++++++++++++++------------
drivers/irqchip/irq-loongson-eiointc.c | 2 +-
drivers/irqchip/irq-qcom-mpm.c | 4 +--
4 files changed, 47 insertions(+), 26 deletions(-)
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next reply other threads:[~2024-02-18 10:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-18 10:38 Borislav Petkov [this message]
2024-02-18 18:22 ` 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=20240218103837.GAZdHeLbPN7pXCkE3L@fat_crate.local \
--to=bp@alien8.de \
--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®