From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: open list <linux-kernel@vger.kernel.org>,
linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
lkft-triage@lists.linaro.org
Cc: Thomas Zimmermann <tzimmermann@suse.de>,
Helge Deller <deller@gmx.de>, Arnd Bergmann <arnd@arndb.de>
Subject: fbdev/chipsfb.c:401:31: error: invalid use of undefined type 'struct backlight_device'
Date: Mon, 4 Mar 2024 13:50:43 +0530 [thread overview]
Message-ID: <CA+G9fYsAk5TbqqxFC2W4oHLGA0CbTHMxbeq8QayFXTU75YiueA@mail.gmail.com> (raw)
The powerpc ppc6xx_defconfig builds failed on today's Linux next tag
next-20240304.
Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
Build log:
---------
drivers/video/fbdev/chipsfb.c: In function 'chipsfb_pci_init':
drivers/video/fbdev/chipsfb.c:401:31: error: invalid use of undefined
type 'struct backlight_device'
401 | pmac_backlight->props.power = FB_BLANK_UNBLANK;
| ^~
Steps to reproduce:
# tuxmake --runtime podman --target-arch powerpc --toolchain gcc-13
--kconfig ppc6xx_defconfig
- https://storage.tuxsuite.com/public/linaro/lkft/builds/2dDE297yLFrAr3gigIDy8tIleDh/tuxmake_reproducer.sh
Links:
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240304/testrun/22919857/suite/build/test/gcc-13-ppc6xx_defconfig/details/
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240304/testrun/22919857/suite/build/test/gcc-13-ppc6xx_defconfig/log
- https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240304/testrun/22919857/suite/build/test/gcc-13-ppc6xx_defconfig/history/
--
Linaro LKFT
https://lkft.linaro.org
next reply other threads:[~2024-03-04 8:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 8:20 Naresh Kamboju [this message]
2024-03-04 9:55 ` [PATCH] powerpc: include linux/backlight.h from asm/backlight.h Jani Nikula
2024-03-04 10:01 ` Jani Nikula
2024-03-04 14:55 ` Naresh Kamboju
2024-03-05 0:39 ` Michael Ellerman
2024-03-05 8:19 ` Jani Nikula
2024-03-04 10:32 ` Thomas Zimmermann
2024-03-04 10:40 ` Thomas Zimmermann
2024-03-04 18:13 ` Christophe Leroy
2024-03-05 0:36 ` Michael Ellerman
2024-03-05 8:09 ` Thomas Zimmermann
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=CA+G9fYsAk5TbqqxFC2W4oHLGA0CbTHMxbeq8QayFXTU75YiueA@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--cc=arnd@arndb.de \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).