From: Pavel Machek <pavel@denx.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, allen.lkml@gmail.com, broonie@kernel.org
Subject: Re: [PATCH 6.1 000/141] 6.1.88-rc1 review
Date: Wed, 24 Apr 2024 09:21:13 +0200 [thread overview]
Message-ID: <Ziiy6cS8Yyg6VFfK@duo.ucw.cz> (raw)
In-Reply-To: <20240423213853.356988651@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 4023 bytes --]
Hi!
> This is the start of the stable review cycle for the 6.1.88 release.
> There are 141 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
This causes compilation errors in our testing:
arch/arm/mach-omap2/pdata-quirks.c:259:15: error: variable 'pandora_soc_audio_gpios' has initializer but incomplete type
1991 259 | static struct gpiod_lookup_table pandora_soc_audio_gpios = {
1992 | ^~~~~~~~~~~~~~~~~~
1993arch/arm/mach-omap2/pdata-quirks.c:260:10: error: 'struct gpiod_lookup_table' has no member named 'dev_id'
1994 260 | .dev_id = "soc-audio",
1995 | ^~~~~~
1996arch/arm/mach-omap2/pdata-quirks.c:260:19: warning: excess elements in struct initializer
1997 260 | .dev_id = "soc-audio",
1998 | ^~~~~~~~~~~
1999arch/arm/mach-omap2/pdata-quirks.c:260:19: note: (near initialization for 'pandora_soc_audio_gpios')
2000arch/arm/mach-omap2/pdata-quirks.c:261:10: error: 'struct gpiod_lookup_table' has no member named 'table'
2001 261 | .table = {
2002 | ^~~~~
2003arch/arm/mach-omap2/pdata-quirks.c:261:18: error: extra brace group at end of initializer
2004 261 | .table = {
2005 | ^
2006arch/arm/mach-omap2/pdata-quirks.c:261:18: note: (near initialization for 'pandora_soc_audio_gpios')
2007arch/arm/mach-omap2/pdata-quirks.c:262:17: error: implicit declaration of function 'GPIO_LOOKUP'; did you mean 'IOP_LOOKUP'? [-Werror=implicit-function-declaration]
2008 262 | GPIO_LOOKUP("gpio-112-127", 6, "dac", GPIO_ACTIVE_HIGH),
2009 | ^~~~~~~~~~~
2010 | IOP_LOOKUP
2011arch/arm/mach-omap2/pdata-quirks.c:262:55: error: 'GPIO_ACTIVE_HIGH' undeclared here (not in a function); did you mean 'ACPI_ACTIVE_HIGH'?
2012 262 | GPIO_LOOKUP("gpio-112-127", 6, "dac", GPIO_ACTIVE_HIGH),
2013 | ^~~~~~~~~~~~~~~~
2014 | ACPI_ACTIVE_HIGH
2015arch/arm/mach-omap2/pdata-quirks.c:264:17: error: extra brace group at end of initializer
2016 264 | { }
2017 | ^
2018arch/arm/mach-omap2/pdata-quirks.c:264:17: note: (near initialization for 'pandora_soc_audio_gpios')
2019arch/arm/mach-omap2/pdata-quirks.c:261:18: warning: excess elements in struct initializer
2020 261 | .table = {
2021 | ^
2022arch/arm/mach-omap2/pdata-quirks.c:261:18: note: (near initialization for 'pandora_soc_audio_gpios')
2023 CC net/sched/sch_api.o
2024arch/arm/mach-omap2/pdata-quirks.c: In function 'omap3_pandora_legacy_init':
2025arch/arm/mach-omap2/pdata-quirks.c:271:9: error: implicit declaration of function 'gpiod_add_lookup_table' [-Werror=implicit-function-declaration]
2026 271 | gpiod_add_lookup_table(&pandora_soc_audio_gpios);
2027 | ^~~~~~~~~~~~~~~~~~~~~~
2028arch/arm/mach-omap2/pdata-quirks.c: At top level:
2029arch/arm/mach-omap2/pdata-quirks.c:259:34: error: storage size of 'pandora_soc_audio_gpios' isn't known
2030 259 | static struct gpiod_lookup_table pandora_soc_audio_gpios = {
2031 | ^~~~~~~~~~~~~~~~~~~~~~~
2032cc1: some warnings being treated as errors
2033make[2]: *** [scripts/Makefile.build:250: arch/arm/mach-omap2/pdata-quirks.o] Error 1
2034make[1]: *** [scripts/Makefile.build:500: arch/arm/mach-omap2] Error 2
2035make[1]: *** Waiting for unfinished jobs....
2036
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/jobs/6700371466
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/1265143103
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2024-04-24 7:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 21:37 Greg Kroah-Hartman
2024-04-23 23:00 ` SeongJae Park
2024-04-24 7:21 ` Pavel Machek [this message]
2024-04-24 8:23 ` Naresh Kamboju
2024-04-28 12:32 ` Vitaly Chikunov
2024-04-28 16:24 ` Guenter Roeck
2024-04-29 10:21 ` Greg Kroah-Hartman
2024-04-24 8:26 ` Ron Economos
2024-04-24 16:26 ` Florian Fainelli
2024-04-25 9:02 ` Jon Hunter
2024-04-25 9:03 ` Yann Sionneau
2024-04-25 19:27 ` Mateusz Jończyk
2024-04-25 20:08 ` Shreeya Patel
2024-04-26 2:21 ` Mark Brown
2024-04-26 10:44 ` Pavel Machek
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=Ziiy6cS8Yyg6VFfK@duo.ucw.cz \
--to=pavel@denx.de \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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®