From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Inki Dae <daeinki@gmail•com>
Cc: Inki Dae <inki.dae@samsung•com>,
Kaustabh Chakraborty <kauschluss@disroot•org>,
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 drm-exynos tree
Date: Thu, 21 Aug 2025 11:27:40 +1000 [thread overview]
Message-ID: <20250821112740.75a41814@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 604 bytes --]
Hi all,
After merging the drm-exynos tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
drivers/gpu/drm/exynos/exynos_drm_dsi.c:158:20: error: 'DSIM_TYPE_EXYNOS7870' undeclared here (not in a function); did you mean 'DSIM_TYPE_EXYNOS5410'?
158 | .hw_type = DSIM_TYPE_EXYNOS7870,
| ^~~~~~~~~~~~~~~~~~~~
| DSIM_TYPE_EXYNOS5410
Caused by commit
d07e4c00696f ("drm/exynos: dsi: add support for exynos7870")
I have used the drm-exynos tree from next-20250820 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-08-21 1:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 1:27 Stephen Rothwell [this message]
2025-08-26 2:13 ` linux-next: build failure after merge of the drm-exynos tree Stephen Rothwell
2025-09-01 2:22 ` Stephen Rothwell
2025-09-02 3:03 ` Stephen Rothwell
2025-09-03 15:51 ` Kaustabh Chakraborty
2025-09-03 21:59 ` Stephen Rothwell
2025-09-12 2:47 ` Stephen Rothwell
2025-09-28 15:31 ` Kaustabh Chakraborty
-- strict thread matches above, loose matches on Subject: below --
2015-08-17 3:51 Stephen Rothwell
2015-08-17 3:53 ` Stephen Rothwell
2015-08-17 5:53 ` Stephen Rothwell
2015-08-17 7:08 ` Inki Dae
2015-08-18 3:02 ` Stephen Rothwell
2015-06-23 1:52 Stephen Rothwell
2015-06-23 5:30 ` Inki Dae
2015-06-24 1:01 ` Stephen Rothwell
2015-06-24 1:21 ` Inki Dae
2015-06-24 1:25 ` Dave Airlie
2015-06-24 1:25 ` Inki Dae
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=20250821112740.75a41814@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=daeinki@gmail$(echo .)com \
--cc=inki.dae@samsung$(echo .)com \
--cc=kauschluss@disroot$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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