From: Mark Brown <broonie@kernel.org>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Armin Wolf <W_Armin@gmx.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the pagemap-headers tree
Date: Thu, 24 Sep 2026 19:17:42 +0100 [thread overview]
Message-ID: <arVpRvAzgfZkSHDF@sirena.org.uk> (raw)
Hi all,
After merging the pagemap-headers tree, today's linux-next build
(powerpc ppc4xx_defconfig) failed like this:
In file included from /tmp/next/build/include/linux/preempt.h:11,
from /tmp/next/build/include/linux/alloc_tag.h:11,
from /tmp/next/build/include/linux/percpu.h:5,
from /tmp/next/build/arch/powerpc/include/asm/time.h:14,
from /tmp/next/build/arch/powerpc/platforms/44x/sam440ep.c:21:
/tmp/next/build/include/linux/acpi.h: In function '__free_acpi_object_free':
/tmp/next/build/include/linux/cleanup.h:211:92: error: suggest braces around empty body in an 'if' statement [-Werror=empty-body]
211 | static __always_inline void __free_##_name(void *p) { _type _T = *(_type *)p; _free; }
| ^
/tmp/next/build/include/linux/acpi.h:31:1: note: in expansion of macro 'DEFINE_FREE'
31 | DEFINE_FREE(acpi_object_free, union acpi_object *, if (_T) ACPI_FREE(_T));
| ^~~~~~~~~~~
cc1: all warnings being treated as errors
make[6]: *** [/tmp/next/build/scripts/Makefile.build:290: arch/powerpc/platforms/44x/sam440ep.o] Error 1
make[6]: *** Waiting for unfinished jobs....
In file included from /tmp/next/build/include/linux/preempt.h:11,
from /tmp/next/build/include/linux/sched.h:15,
from /tmp/next/build/include/linux/ratelimit.h:6,
from /tmp/next/build/include/linux/dev_printk.h:16,
from /tmp/next/build/include/linux/device.h:15,
from /tmp/next/build/include/linux/platform_device.h:13,
from /tmp/next/build/arch/powerpc/platforms/44x/warp.c:11:
/tmp/next/build/include/linux/acpi.h: In function '__free_acpi_object_free':
/tmp/next/build/include/linux/cleanup.h:211:92: error: suggest braces around empty body in an 'if' statement [-Werror=empty-body]
211 | static __always_inline void __free_##_name(void *p) { _type _T = *(_type *)p; _free; }
| ^
/tmp/next/build/include/linux/acpi.h:31:1: note: in expansion of macro 'DEFINE_FREE'
31 | DEFINE_FREE(acpi_object_free, union acpi_object *, if (_T) ACPI_FREE(_T));
| ^~~~~~~~~~~
cc1: all warnings being treated as errors
Caused by commit
f54586fcd661e (ACPI: fan: Use __free() to simplify AML error handling)
(it was also causing lots of warnings in other GCC configurations but
didn't trip -Werror in allmodconfig since it doesn't seem to upset
clang.). I have reverted that commit for today.
next reply other threads:[~2026-09-24 18:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 18:17 Mark Brown [this message]
2026-09-24 20:27 ` linux-next: build failure after merge of the pagemap-headers tree Wysocki, Rafael J
-- strict thread matches above, loose matches on Subject: below --
2026-09-08 20:53 Mark Brown
2026-08-25 13:35 Mark Brown
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=arVpRvAzgfZkSHDF@sirena.org.uk \
--to=broonie@kernel.org \
--cc=W_Armin@gmx.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rafael.j.wysocki@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.