mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Ulf Hansson <ulfh@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the pmdomain-fixes tree
Date: Tue, 10 Nov 2026 18:56:15 +0000	[thread overview]
Message-ID: <60f76f85-8a5f-4b3e-afec-ab4e69315ff5@sirena.org.uk> (raw)
In-Reply-To: <avNHazNbGtMQJ5pV@sirena.org.uk>

[-- Attachment #1: Type: text/plain, Size: 5505 bytes --]

On Tue, Nov 10, 2026 at 04:33:51PM +0000, Mark Brown wrote:
> Hi all,
> 
> After merging the pmdomain-fixes tree, today's linux-next build
> (arm multi_v7_defconfig) failed like this:

This also affects the pmdomain tree.  Also, I still had your Linaro
address as a contact for all your trees - I've updated this to your
kernel.org one since the Linaro one started bouncing.

> In file included from /tmp/next/build/include/linux/device.h:32,
>                  from /tmp/next/build/include/linux/platform_device.h:13,
>                  from /tmp/next/build/drivers/pmdomain/imx/gpc.c:11:
> /tmp/next/build/drivers/pmdomain/imx/gpc.c: In function 'imx_gpc_remove':
> /tmp/next/build/drivers/pmdomain/imx/gpc.c:554:25: error: invalid storage class for function 'imx_gpc_driver_init'
>   554 | builtin_platform_driver(imx_gpc_driver)
>       |                         ^~~~~~~~~~~~~~
> /tmp/next/build/include/linux/device/driver.h:294:19: note: in definition of macro 'builtin_driver'
>   294 | static int __init __driver##_init(void) \
>       |                   ^~~~~~~~
> /tmp/next/build/drivers/pmdomain/imx/gpc.c:554:1: note: in expansion of macro 'builtin_platform_driver'
>   554 | builtin_platform_driver(imx_gpc_driver)
>       | ^~~~~~~~~~~~~~~~~~~~~~~
> In file included from /tmp/next/build/include/linux/printk.h:6,
>                  from /tmp/next/build/include/asm-generic/bug.h:31,
>                  from /tmp/next/build/arch/arm/include/asm/bug.h:60,
>                  from /tmp/next/build/include/linux/bug.h:5,
>                  from /tmp/next/build/include/linux/instrumented.h:10,
>                  from /tmp/next/build/include/linux/atomic/atomic-instrumented.h:17,
>                  from /tmp/next/build/include/linux/atomic.h:82,
>                  from /tmp/next/build/include/asm-generic/bitops/lock.h:5,
>                  from /tmp/next/build/arch/arm/include/asm/bitops.h:245,
>                  from /tmp/next/build/include/linux/bitops.h:67,
>                  from /tmp/next/build/include/linux/kernel.h:23,
>                  from /tmp/next/build/include/linux/clk.h:13,
>                  from /tmp/next/build/drivers/pmdomain/imx/gpc.c:7:
> /tmp/next/build/drivers/pmdomain/imx/gpc.c:554:25: error: initializer element is not constant
>   554 | builtin_platform_driver(imx_gpc_driver)
>       |                         ^~~~~~~~~~~~~~
> /tmp/next/build/include/linux/init.h:265:55: note: in definition of macro '____define_initcall'
>   265 |                 __attribute__((__section__(__sec))) = fn;
>       |                                                       ^~
> /tmp/next/build/include/linux/init.h:275:9: note: in expansion of macro '__unique_initcall'
>   275 |         __unique_initcall(fn, id, __sec, __initcall_id(fn))
>       |         ^~~~~~~~~~~~~~~~~
> /tmp/next/build/include/linux/init.h:277:35: note: in expansion of macro '___define_initcall'
>   277 | #define __define_initcall(fn, id) ___define_initcall(fn, id, .initcall##id)
>       |                                   ^~~~~~~~~~~~~~~~~~
> /tmp/next/build/include/linux/init.h:306:41: note: in expansion of macro '__define_initcall'
>   306 | #define device_initcall(fn)             __define_initcall(fn, 6)
>       |                                         ^~~~~~~~~~~~~~~~~
> /tmp/next/build/include/linux/device/driver.h:298:1: note: in expansion of macro 'device_initcall'
>   298 | device_initcall(__driver##_init);
>       | ^~~~~~~~~~~~~~~
> /tmp/next/build/include/linux/platform_device.h:345:9: note: in expansion of macro 'builtin_driver'
>   345 |         builtin_driver(__platform_driver, platform_driver_register)
>       |         ^~~~~~~~~~~~~~
> /tmp/next/build/drivers/pmdomain/imx/gpc.c:554:1: note: in expansion of macro 'builtin_platform_driver'
>   554 | builtin_platform_driver(imx_gpc_driver)
>       | ^~~~~~~~~~~~~~~~~~~~~~~
> /tmp/next/build/include/linux/init.h:176:30: error: expected declaration or statement at end of input
>   176 | #define THIS_MODULE ((struct module *)0)
>       |                              ^~~~~~
> /tmp/next/build/include/linux/platform_device.h:304:41: note: in expansion of macro 'THIS_MODULE'
>   304 |         __platform_driver_register(drv, THIS_MODULE, KBUILD_MODNAME)
>       |                                         ^~~~~~~~~~~
> /tmp/next/build/include/linux/device/driver.h:296:16: note: in expansion of macro 'platform_driver_register'
>   296 |         return __register(&(__driver) , ##__VA_ARGS__); \
>       |                ^~~~~~~~~~
> /tmp/next/build/include/linux/platform_device.h:345:9: note: in expansion of macro 'builtin_driver'
>   345 |         builtin_driver(__platform_driver, platform_driver_register)
>       |         ^~~~~~~~~~~~~~
> /tmp/next/build/drivers/pmdomain/imx/gpc.c:554:1: note: in expansion of macro 'builtin_platform_driver'
>   554 | builtin_platform_driver(imx_gpc_driver)
>       | ^~~~~~~~~~~~~~~~~~~~~~~
> /tmp/next/build/drivers/pmdomain/imx/gpc.c: At top level:
> /tmp/next/build/drivers/pmdomain/imx/gpc.c:503:13: warning: 'imx_gpc_remove' defined but not used [-Wunused-function]
>   503 | static void imx_gpc_remove(struct platform_device *pdev)
>       |             ^~~~~~~~~~~~~~
> 
> AFAICT this is caused by commit
> 
>    d7262971a2acc (pmdomain: imx: gpc: remove all initialized power domains)
> 
> though I don't really see how.  I have used the tree from next-20261109
> instead.



[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      parent reply	other threads:[~2026-11-10 18:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-10 16:33 Mark Brown
2026-11-10 17:02 ` Sasha Levin
2026-11-10 17:07   ` Mark Brown
2026-11-10 18:56 ` Mark Brown [this message]

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=60f76f85-8a5f-4b3e-afec-ab4e69315ff5@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ulfh@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®