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>,
Dave Airlie <airlied@redhat.com>,
DRI <dri-devel@lists.freedesktop.org>
Subject: Re: linux-next: build failure after merge of the drm-exynos tree
Date: Tue, 2 Sep 2025 13:03:04 +1000 [thread overview]
Message-ID: <20250902130304.1f80f4c6@canb.auug.org.au> (raw)
In-Reply-To: <20250901122226.20a39858@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]
Hi all,
On Mon, 1 Sep 2025 12:22:26 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> On Tue, 26 Aug 2025 12:13:20 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > On Thu, 21 Aug 2025 11:27:40 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > >
> > > 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.
> >
> > I am still seeing this failure.
>
> I am still seeing this failure.
Today, I have just reverted that commit instead of the whole branch,
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-09-02 3:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250821112740.75a41814@canb.auug.org.au>
[not found] ` <20250826121320.4931c6eb@canb.auug.org.au>
2025-09-01 2:22 ` linux-next: build failure after merge of the drm-exynos tree Stephen Rothwell
2025-09-02 3:03 ` Stephen Rothwell [this message]
2025-09-03 15:51 ` Kaustabh Chakraborty
2025-09-03 21:59 ` Stephen Rothwell
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=20250902130304.1f80f4c6@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=airlied@redhat.com \
--cc=daeinki@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=inki.dae@samsung.com \
--cc=kauschluss@disroot.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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 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).