From: Marc Zyngier <maz@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Jiaxun Yang <jiaxun.yang@flygoat.com>,
Palmer Dabbelt <palmerdabbelt@google.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Jason Cooper <jason@lakedaemon.net>,
kernel-team@android.com, linux-kernel@vger.kernel.org
Subject: [GIT PULL] irqchip fixes for 5.8, take #1
Date: Sat, 27 Jun 2020 11:51:03 +0100 [thread overview]
Message-ID: <20200627105103.92465-1-maz@kernel.org> (raw)
Hi Thomas,
Here's a small pull request for a few fixes that have accumulated over
the past few weeks. The most interesting one is an atomicity update in
the GIC set_affinity callback, which could race against the update of
another 3 adjacent interrupts (I broke it 4 years ago, and nobody
noticed...). The other bug is a nice GICv4.1 sleep-in-atomic found by
Zenghui. The rest fixes a couple of typos.
Please pull,
M.
The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:
Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git tags/irqchip-fixes-5.8-1
for you to fetch changes up to 005c34ae4b44f085120d7f371121ec7ded677761:
irqchip/gic: Atomically update affinity (2020-06-21 15:24:46 +0100)
----------------------------------------------------------------
irqchip fixes for Linux 5.8, take #1
- Fix atomicity of affinity update in the GIC driver
- Don't sleep in atomic when waiting for a GICv4.1 RD to respond
- Fix a couple of typos in user-visible messages
----------------------------------------------------------------
Jiaxun Yang (1):
irqchip/loongson-pci-msi: Fix a typo in Kconfig
Marc Zyngier (1):
irqchip/gic: Atomically update affinity
Palmer Dabbelt (1):
irqchip/riscv-intc: Fix a typo in a pr_warn()
Zenghui Yu (1):
irqchip/gic-v4.1: Use readx_poll_timeout_atomic() to fix sleep in atomic
drivers/irqchip/Kconfig | 2 +-
drivers/irqchip/irq-gic-v3-its.c | 8 ++++----
drivers/irqchip/irq-gic.c | 14 +++-----------
drivers/irqchip/irq-riscv-intc.c | 2 +-
4 files changed, 9 insertions(+), 17 deletions(-)
reply other threads:[~2020-06-27 10:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200627105103.92465-1-maz@kernel.org \
--to=maz@kernel.org \
--cc=jason@lakedaemon.net \
--cc=jiaxun.yang@flygoat.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=palmerdabbelt@google.com \
--cc=tglx@linutronix.de \
--cc=yuzenghui@huawei.com \
/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