From: "Markus Stockhausen" <markus.stockhausen@gmx.de>
To: "'Haofeng Li'" <920484857@qq.com>, <tglx@kernel.org>
Cc: <linux-kernel@vger.kernel.org>,
"'Haofeng Li'" <13266079573@163.com>,
"'Haofeng Li'" <lihaofeng@kylinos.cn>
Subject: AW: [PATCH 12/16] irqchip/realtek-rtl: unmap per-CPU bases on init failure
Date: Wed, 15 Jul 2026 08:12:10 +0200 [thread overview]
Message-ID: <007e01dd1420$e0175f40$a0461dc0$@gmx.de> (raw)
In-Reply-To: <tencent_DD406F972C4DFBCA9E5F60235B1412F4C006@qq.com>
> Von: Haofeng Li <920484857@qq.com>
> Gesendet: Dienstag, 14. Juli 2026 15:25
> An: tglx@kernel.org
> Betreff: [PATCH 12/16] irqchip/realtek-rtl: unmap per-CPU bases on init
failure
>
> From: Haofeng Li <lihaofeng@kylinos.cn>
>
> realtek_rtl_of_init() maps a separate register base for every present
> CPU. If mapping CPU n fails, mappings for earlier CPUs remain. Parent
> IRQ lookup and domain creation failures also leave all per-CPU mappings
> allocated.
>
> Add realtek_rtl_unmap_bases() and use it on every error path after
> mapping starts.
>
> Fixes: a1a35c09241f ("irqchip/irq-realtek-rtl: Add multicore support")
> Signed-off-by: Haofeng Li <lihaofeng@kylinos.cn>
Reviewed-by: Markus Stockhausen <markus.stockhausen@gmx.de>
Thanks for the fix.
Markus
next prev parent reply other threads:[~2026-07-15 6:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 12:23 [PATCH 00/16] irqchip: harden initialization error paths Haofeng Li
2026-07-14 12:23 ` [PATCH 01/16] irqchip/riscv-imsic: fix MMIO lookup OOB and NULL cleanup Haofeng Li
2026-07-14 13:15 ` Anup Patel
2026-07-14 12:23 ` [PATCH 02/16] irqchip/loongarch-ir: fix redirect free and alloc leaks Haofeng Li
2026-07-14 13:24 ` [PATCH 03/16] irqchip/sifive-plic: do not iounmap devm mappings Haofeng Li
2026-07-14 15:05 ` Anup Patel
[not found] ` <20260714132453.3302672-1-920484857@qq.com>
2026-07-14 13:24 ` [PATCH 04/16] irqchip/crossbar: fix allocation and init cleanup Haofeng Li
2026-07-14 13:24 ` [PATCH 05/16] irqchip/bcm7038-l1: clean up init failure paths Haofeng Li
2026-07-14 13:24 ` [PATCH 06/16] irqchip/loongson-liointc: unmap per-core iomaps on error Haofeng Li
2026-07-14 13:24 ` [PATCH 07/16] irqchip/mips-gic: clean up IRQ domain creation failure Haofeng Li
2026-07-14 13:24 ` [PATCH 08/16] irqchip/mips-gic: clean up if IPI domain registration fails Haofeng Li
2026-07-14 13:24 ` [PATCH 09/16] irqchip/econet: clean up VEIC initialization Haofeng Li
2026-07-14 13:24 ` [PATCH 10/16] irqchip/aspeed-vic: publish handler only after domain creation Haofeng Li
2026-07-14 13:24 ` [PATCH 11/16] irqchip/loongson-eiointc: preserve live state on cascade failure Haofeng Li
2026-07-14 13:24 ` [PATCH 12/16] irqchip/realtek-rtl: unmap per-CPU bases on init failure Haofeng Li
2026-07-15 6:12 ` Markus Stockhausen [this message]
2026-07-14 13:24 ` [PATCH 13/16] irqchip/realtek-rtl: dispose parent mapping on domain failure Haofeng Li
2026-07-14 13:24 ` [PATCH 14/16] irqchip/renesas-rzg2l: fix wrong errno in reset error log Haofeng Li
2026-07-14 13:24 ` [PATCH 15/16] irqchip/gic-v3: fail T241 quirk if alias ioremap fails Haofeng Li
2026-07-14 14:53 ` Marc Zyngier
2026-07-14 13:24 ` [PATCH 16/16] irqchip/bcm7120-l2: fix parent IRQ count error handling Haofeng Li
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='007e01dd1420$e0175f40$a0461dc0$@gmx.de' \
--to=markus.stockhausen@gmx.de \
--cc=13266079573@163.com \
--cc=920484857@qq.com \
--cc=lihaofeng@kylinos.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@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