| Context |
Check |
Description |
| bjorn/pre-ci_am |
success
|
Success
|
| bjorn/build-rv32-defconfig |
success
|
build-rv32-defconfig
|
| bjorn/build-rv64-clang-allmodconfig |
success
|
build-rv64-clang-allmodconfig
|
| bjorn/build-rv64-gcc-allmodconfig |
success
|
build-rv64-gcc-allmodconfig
|
| bjorn/build-rv64-nommu-k210-defconfig |
success
|
build-rv64-nommu-k210-defconfig
|
| bjorn/build-rv64-nommu-k210-virt |
success
|
build-rv64-nommu-k210-virt
|
| bjorn/checkpatch |
warning
|
checkpatch
|
| bjorn/dtb-warn-rv64 |
success
|
dtb-warn-rv64
|
| bjorn/header-inline |
success
|
header-inline
|
| bjorn/kdoc |
success
|
kdoc
|
| bjorn/module-param |
success
|
module-param
|
| bjorn/verify-fixes |
success
|
verify-fixes
|
| bjorn/verify-signedoff |
success
|
verify-signedoff
|
@@ -37,7 +37,7 @@ bool irq_fixup_move_pending(struct irq_d
void irq_force_complete_move(struct irq_desc *desc)
{
- for (struct irq_data *d = irq_desc_get_irq_data(desc); d; d = d->parent_data) {
+ for (struct irq_data *d = irq_desc_get_irq_data(desc); d; d = irqd_get_parent_data(d)) {
if (d->chip && d->chip->irq_force_complete_move) {
d->chip->irq_force_complete_move(d);
return;
Frank reported, that the common irq_force_complete_move() breaks the out of tree build of ia64. The reason is that ia64 uses the migration code, but does not have hierarchical interrupt domains enabled. This went unnoticed in mainline as both x86 and RISC-V have hierarchical domains enabled. Not that it matters for mainline, but it's still inconsistent. Use irqd_get_parent_data() instead of accessing the parent_data field directly. The helper returns NULL when hierarchical domains are disabled otherwise it accesses the parent_data field of the domain. No functional change. Fixes: 751dc837dabd ("genirq: Introduce common irq_force_complete_move() implementation") Reported-by: Frank Scheiner <frank.scheiner@web.de> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Tested-by: Frank Scheiner <frank.scheiner@web.de>