intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Simona Vetter <simona.vetter@ffwll.ch>,
	dri-devel@lists.freedesktop.org
Cc: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
	Intel Graphics <intel-gfx@lists.freedesktop.org>,
	DRI <dri-devel@lists.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Damon Ding <damon.ding@rock-chips.com>
Subject: Re: linux-next: build failure after merge of the drm-misc tree
Date: Wed, 28 May 2025 10:27:19 +0200	[thread overview]
Message-ID: <9453742.CDJkKcVGEf@diego> (raw)
In-Reply-To: <64499337-fc61-42b0-8c50-7749b2036c54@rock-chips.com>

Hi,

Am Mittwoch, 28. Mai 2025, 09:17:13 Mitteleuropäische Sommerzeit schrieb Damon Ding:
> On 2025/5/28 11:42, Stephen Rothwell wrote:
> > Hi all,
> > 
> > After merging the drm-misc tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
> > 
> > drivers/gpu/drm/bridge/analogix/analogix_dp_core.c: In function 'analogix_dp_probe':
> > drivers/gpu/drm/bridge/analogix/analogix_dp_core.c:1589:17: error: label 'err_disable_clk' used but not defined
> >   1589 |                 goto err_disable_clk;
> >        |                 ^~~~
> > 
> > Caused by commit
> > 
> >    6579a03e68ff ("drm/bridge: analogix_dp: Remove the unnecessary calls to clk_disable_unprepare() during probing")
> > 
> > I have used the drm-misc tree from next-20250527 for today.
> > 
> 
> Oh, I have found the same compile error after rebasing.
> 
> I have removed the 'err_disable_clk' flag and made it return 
> ERR_PTR(ret) in:
> https://lore.kernel.org/all/20250310104114.2608063-7-damon.ding@rock-chips.com/
> 
> Likely a small merge conflict bug. Will patch it later. ;-)

I have sent in a patch for that issue yesterday, in

https://lore.kernel.org/dri-devel/20250527225120.3361663-1-heiko@sntech.de/


Heiko



  reply	other threads:[~2025-05-28  9:10 UTC|newest]

Thread overview: 114+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-28  3:42 linux-next: build failure after merge of the drm-misc tree Stephen Rothwell
2025-05-28  7:17 ` Damon Ding
2025-05-28  8:27   ` Heiko Stübner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-29  2:23 Stephen Rothwell
2025-08-29  8:01 ` Danilo Krummrich
2025-07-15  3:55 Stephen Rothwell
2025-02-13  0:38 Stephen Rothwell
2024-12-09  1:17 Stephen Rothwell
2024-09-04  2:52 Stephen Rothwell
2024-09-04  9:57 ` Jani Nikula
2024-09-04 11:25   ` Robert Foss
2024-05-29  2:35 Stephen Rothwell
2024-05-29  8:21 ` Maxime Ripard
2024-05-29  2:29 Stephen Rothwell
2024-04-02 23:47 Stephen Rothwell
2024-02-22  1:46 Stephen Rothwell
2024-02-22  8:14 ` Biju Das
2024-02-22  8:29   ` Geert Uytterhoeven
2024-02-22  9:16     ` Biju Das
2024-02-22  8:32   ` Maxime Ripard
2024-02-22  8:49     ` Biju Das
2024-02-13  1:04 Stephen Rothwell
2024-02-12  1:26 Stephen Rothwell
2024-02-12  9:12 ` Jani Nikula
2024-02-12 13:09   ` Jani Nikula
2024-02-06  4:28 Stephen Rothwell
2024-02-12  1:25 ` Stephen Rothwell
2024-02-12 13:15 ` Jani Nikula
2024-02-19 21:48   ` Stephen Rothwell
2024-02-25 21:41     ` Stephen Rothwell
2024-02-25 21:47       ` Stephen Rothwell
2024-02-26 12:56         ` Christian König
2024-02-06  1:28 Stephen Rothwell
2024-02-06 11:46 ` Jani Nikula
2024-02-06 12:39 ` Thomas Hellström
2024-02-07  2:46 ` Stephen Rothwell
2019-10-16  0:22 Stephen Rothwell
2019-10-16 16:21 ` Alex Deucher
2019-10-09  0:35 Stephen Rothwell
2019-10-09 16:17 ` Alex Deucher
2019-10-07 23:30 Stephen Rothwell
2019-10-08  3:02 ` Stephen Rothwell
2019-10-08  7:56 ` Hans Verkuil
2019-10-14  0:12 ` Stephen Rothwell
2019-08-28  8:55 Stephen Rothwell
2019-08-28  9:15 ` Gerd Hoffmann
2019-08-07  3:21 Stephen Rothwell
2019-08-01  2:30 Stephen Rothwell
2019-06-14  4:41 Stephen Rothwell
2019-04-09  6:08 Stephen Rothwell
2019-04-09  7:22 ` Gerd Hoffmann
2019-04-09  8:08   ` Stephen Rothwell
2019-04-09  8:31     ` Gerd Hoffmann
2019-04-05  4:55 Stephen Rothwell
2019-04-05  6:03 ` Stephen Rothwell
2019-04-01 23:50 Stephen Rothwell
2019-04-02  5:55 ` Qiang Yu
2019-04-02  7:57   ` Daniel Vetter
2019-04-02  8:59     ` Qiang Yu
2019-04-02  9:08       ` Daniel Vetter
2019-04-02 11:26   ` Matthew Wilcox
2019-04-02 13:56     ` Qiang Yu
2019-04-02 14:10       ` Matthew Wilcox
2019-04-02 11:21 ` Matthew Wilcox
2019-04-02 13:33   ` Qiang Yu
2019-02-08  1:38 Stephen Rothwell
2019-02-08  8:52 ` Daniel Vetter
2019-02-08 22:17   ` Sam Ravnborg
2019-01-08  0:12 Stephen Rothwell
2019-01-08  8:37 ` Daniel Vetter
2019-01-08 14:01   ` Kazlauskas, Nicholas
2019-01-09  0:29   ` Stephen Rothwell
2018-12-06  2:32 Stephen Rothwell
2018-12-07 12:37 ` Koenig, Christian
2017-12-06  1:00 Stephen Rothwell
2017-07-19  1:46 Stephen Rothwell
2017-07-21  0:08 ` Stephen Rothwell
2017-07-21  7:24   ` Daniel Vetter
2017-07-21 19:01     ` Hans de Goede
2017-07-24  0:03     ` Stephen Rothwell
2017-07-24  8:24       ` Daniel Vetter
2017-07-24 18:33         ` Greg KH
2017-07-18  1:38 Stephen Rothwell
2017-04-21  2:10 Stephen Rothwell
2017-04-21  5:03 ` Logan Gunthorpe
2017-04-24  1:25 ` Stephen Rothwell
2017-05-02  8:25   ` Daniel Vetter
2017-05-02  8:41     ` Stephen Rothwell
2017-05-02  8:55       ` Arnd Bergmann
2017-05-02  9:34         ` Daniel Vetter
2017-05-03 23:50 ` Stephen Rothwell
2017-04-03  3:31 Stephen Rothwell
2017-04-03 17:26 ` Sinclair Yeh
2017-01-05  0:53 Stephen Rothwell
2017-01-05 10:24 ` [Intel-gfx] " Jani Nikula
2017-01-05 10:46   ` Stephen Rothwell
2016-11-09  0:14 Stephen Rothwell
2016-10-24  0:24 Stephen Rothwell
2016-02-10  1:24 Stephen Rothwell
2016-02-10  6:31 ` Daniel Vetter
2016-02-10  8:41 ` Lukas Wunner
2016-02-10 13:17   ` Lukas Wunner
2016-02-10 13:37     ` Daniel Vetter
2015-12-08  0:20 Stephen Rothwell
2015-10-01  2:47 Stephen Rothwell
2015-10-01  6:41 ` Daniel Vetter
2015-09-03  0:49 Stephen Rothwell
2015-09-07 23:42 ` Stephen Rothwell
2015-09-08  4:48   ` Maarten Lankhorst
2015-09-08  8:16     ` Daniel Vetter
2015-07-14  2:52 Stephen Rothwell
2015-07-14  5:00 ` Archit Taneja
2015-07-14  7:36   ` Daniel Vetter
2015-02-24  0:41 Stephen Rothwell
2015-02-24  0:59 ` Daniel Vetter

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=9453742.CDJkKcVGEf@diego \
    --to=heiko@sntech.de \
    --cc=damon.ding@rock-chips.com \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=simona.vetter@ffwll.ch \
    /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).