From: Greg KH <greg@kroah.com>
To: KernelCI bot <bot@kernelci.org>
Cc: kernelci-results@groups.io, stable@vger.kernel.org, gus@collabora.com
Subject: Re: stable-rc/linux-5.4.y: new build regression: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ...
Date: Tue, 4 Feb 2025 11:36:10 +0100 [thread overview]
Message-ID: <2025020459-aversion-recount-0c44@gregkh> (raw)
In-Reply-To: <CACo-S-1EmQkbiykZQYV4yvBZqVe0zNgm9pLYxu6E4bVAPCSrfQ@mail.gmail.com>
On Mon, Feb 03, 2025 at 04:27:00PM -0800, KernelCI bot wrote:
> Hello,
>
> New build issue found on stable-rc/linux-5.4.y:
>
> expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__free’ in
> drivers/soc/atmel/soc.o (drivers/soc/atmel/soc.c)
> [logspec:kbuild,kbuild.compiler.error]
>
> - Dashboard: https://staging.dashboard.kernelci.org:9000/issue/maestro:040dcc33328a47e528c393a656a52b340b4ccc8b
> - Grafana: https://grafana.kernelci.org/d/issue/issue?var-id=maestro:040dcc33328a47e528c393a656a52b340b4ccc8b
>
>
> Log excerpt:
> drivers/soc/atmel/soc.c:277:32: error: expected ‘=’, ‘,’, ‘;’, ‘asm’
> or ‘__attribute__’ before ‘__free’
> 277 | struct device_node *np __free(device_node) =
> of_find_node_by_path("/");
> | ^~~~~~
> drivers/soc/atmel/soc.c:277:32: error: implicit declaration of
> function ‘__free’; did you mean ‘kzfree’?
> [-Werror=implicit-function-declaration]
> 277 | struct device_node *np __free(device_node) =
> of_find_node_by_path("/");
> | ^~~~~~
> | kzfree
> drivers/soc/atmel/soc.c:277:39: error: ‘device_node’ undeclared (first
> use in this function)
> 277 | struct device_node *np __free(device_node) =
> of_find_node_by_path("/");
> | ^~~~~~~~~~~
> drivers/soc/atmel/soc.c:277:39: note: each undeclared identifier is
> reported only once for each function it appears in
> drivers/soc/atmel/soc.c:279:51: error: ‘np’ undeclared (first use in
> this function); did you mean ‘nop’?
> 279 | if (!of_match_node(at91_soc_allowed_list, np))
> | ^~
> | nop
> CC drivers/spi/spidev.o
> cc1: some warnings being treated as errors
>
>
>
> # Builds where the incident occurred:
>
> ## multi_v7_defconfig(gcc-12):
> - Dashboard: https://staging.dashboard.kernelci.org:9000/build/maestro:67a119e4661a7bc87489b6f5
>
> ## multi_v5_defconfig(gcc-12):
> - Dashboard: https://staging.dashboard.kernelci.org:9000/build/maestro:67a119e0661a7bc87489b6f2
>
> ## multi_v7_defconfig(gcc-12):
> - Dashboard: https://staging.dashboard.kernelci.org:9000/build/maestro:67a119d8661a7bc87489b4f0
>
>
> #kernelci issue maestro:040dcc33328a47e528c393a656a52b340b4ccc8b
Now fixed for 5.4, 5.10, and 5.15, thanks!
greg k-h
prev parent reply other threads:[~2025-02-04 10:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 0:27 stable-rc/linux-5.4.y: new build regression: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before KernelCI bot
2025-02-04 10:36 ` Greg KH [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=2025020459-aversion-recount-0c44@gregkh \
--to=greg@kroah.com \
--cc=bot@kernelci.org \
--cc=gus@collabora.com \
--cc=kernelci-results@groups.io \
--cc=stable@vger.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 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.