All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Dave Airlie <airlied@gmail.com>, Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>,
	Suraj Kandpal <suraj.kandpal@intel.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>
Subject: Re: linux-next: build failure after merge of the drm-intel tree
Date: Fri, 28 Jun 2024 12:29:01 +0300	[thread overview]
Message-ID: <87ed8hbele.fsf@intel.com> (raw)
In-Reply-To: <CAPM=9tyNGA2wEgnsKdSyjHRGVikywZLdueZj=syTMFYEUNzxhw@mail.gmail.com>

On Fri, 28 Jun 2024, Dave Airlie <airlied@gmail.com> wrote:
> On Tue, 18 Jun 2024 at 05:26, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
>>
>> On Wed, Jun 12, 2024 at 02:12:39PM +1000, Stephen Rothwell wrote:
>> > Hi all,
>> >
>> > After merging the drm-intel tree, today's linux-next build (i386
>> > defconfig) failed like this:
>> >
>> > x86_64-linux-gnu-ld: drivers/gpu/drm/i915/display/intel_vrr.o: in function `intel_vrr_compute_config':
>> > intel_vrr.c:(.text+0x4e4): undefined reference to `__udivdi3'
>> >
>> > Caused by commit
>> >
>> >   1676ecd303ac ("drm/i915: Compute CMRR and calculate vtotal")
>> >
>> > I have reverted that commit for today.
>>
>> the fixes for that is available in drm-intel-next now. you should probably
>> remove the revert.
>>
>> Thanks for the heads up on that.
>
> In file included from
> /home/airlied/devel/kernel/dim/src/arch/arm/include/asm/div64.h:107,
>                  from /home/airlied/devel/kernel/dim/src/include/linux/math.h:6,
>                  from
> /home/airlied/devel/kernel/dim/src/include/linux/kernel.h:27,
>                  from
> /home/airlied/devel/kernel/dim/src/include/linux/cpumask.h:11,
>                  from /home/airlied/devel/kernel/dim/src/include/linux/smp.h:13,
>                  from
> /home/airlied/devel/kernel/dim/src/include/linux/lockdep.h:14,
>                  from
> /home/airlied/devel/kernel/dim/src/include/linux/spinlock.h:63,
>                  from
> /home/airlied/devel/kernel/dim/src/include/linux/kref.h:16,
>                  from
> /home/airlied/devel/kernel/dim/src/include/drm/drm_device.h:5,
>                  from
> /home/airlied/devel/kernel/dim/src/include/drm/drm_drv.h:35,
>                  from
> /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/xe/compat-i915-headers/i915_drv.h:13,
>                  from
> /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/i915/display/intel_vrr.c:7:
> /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/i915/display/intel_vrr.c:
> In function ‘cmrr_get_vtotal’:
> /home/airlied/devel/kernel/dim/src/include/asm-generic/div64.h:222:35:
> warning: comparison of distinct pointer types lacks a cast
>   222 |         (void)(((typeof((n)) *)0) == ((uint64_t *)0));  \
>       |                                   ^~
> /home/airlied/devel/kernel/dim/src/drivers/gpu/drm/i915/display/intel_vrr.c:155:35:
> note: in expansion of macro ‘do_div’
>   155 |         crtc_state->cmrr.cmrr_m = do_div(adjusted_pixel_rate,
> crtc_state->cmrr.cmrr_n);
>       |                                   ^~~~~~
>
> The fixes might need some more fixing, 32-bit arm build.

Hmm. Works for me with commit 213cc30331e9 ("drm/i915/display: Consider
adjusted_pixel_rate to be u64"). Are you hitting this with drm/next
which doesn't have that yet?

BR,
Jani.


>
> Dave.
>
>>
>> >
>> > --
>> > Cheers,
>> > Stephen Rothwell
>>
>>

-- 
Jani Nikula, Intel

  reply	other threads:[~2024-06-28  9:29 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12  4:12 linux-next: build failure after merge of the drm-intel tree Stephen Rothwell
2024-06-17 19:19 ` Rodrigo Vivi
2024-06-27 21:48   ` Dave Airlie
2024-06-28  9:29     ` Jani Nikula [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-03-16 17:15 Mark Brown
2026-03-17  9:00 ` Jani Nikula
2024-08-29  3:46 Stephen Rothwell
2022-08-26  2:36 Stephen Rothwell
2022-08-26  2:36 ` Stephen Rothwell
2022-08-26  7:50 ` Jani Nikula
2022-08-26  7:50   ` Jani Nikula
2022-04-26  2:08 Stephen Rothwell
2022-04-26  2:08 ` Stephen Rothwell
2022-04-26  7:36 ` Jani Nikula
2022-04-26  7:36   ` Jani Nikula
2022-02-15  1:10 Stephen Rothwell
2022-02-15  1:10 ` Stephen Rothwell
2022-02-15 12:11 ` Jani Nikula
2022-02-15 12:11   ` Jani Nikula
2021-05-21  1:58 Stephen Rothwell
2021-05-21  1:58 ` Stephen Rothwell
2021-01-19 23:57 Stephen Rothwell
2021-01-19 23:57 ` Stephen Rothwell
2021-01-21  1:11 ` Stephen Rothwell
2021-01-21  1:11   ` Stephen Rothwell
2019-12-09 22:39 Stephen Rothwell
2019-12-09 22:42 ` Stephen Rothwell
2019-12-11  9:31   ` Jani Nikula
2019-12-11  9:31     ` Jani Nikula
2019-03-27  2:59 Stephen Rothwell
2019-03-27  2:59 ` Stephen Rothwell
2019-03-27 11:07 ` Joonas Lahtinen
2019-03-27 11:07   ` Joonas Lahtinen
2019-03-27 11:31   ` Stephen Rothwell
2019-03-27 11:31     ` Stephen Rothwell
2018-07-13  1:54 Stephen Rothwell
2018-07-23  2:29 ` Stephen Rothwell
2018-05-08  1:07 Stephen Rothwell
2018-05-08  7:08 ` Oleksandr Andrushchenko
2018-05-08  7:08   ` Oleksandr Andrushchenko
2018-05-09  5:02 ` Stephen Rothwell
2018-05-09  5:02   ` Stephen Rothwell
2018-05-09  5:08   ` Christoph Hellwig
2018-05-09  5:18     ` Stephen Rothwell
2016-10-17 23:59 Stephen Rothwell
2016-10-18  6:26 ` Daniel Vetter
2016-08-23  1:56 Stephen Rothwell
2016-08-23  1:56 ` Stephen Rothwell
2016-08-23 16:33 ` Daniel Vetter
2016-08-23 16:33   ` Daniel Vetter
2016-05-23  2:24 Stephen Rothwell
2016-05-23  2:24 ` Stephen Rothwell
2014-04-03  1:24 Stephen Rothwell
2014-04-03  1:24 ` Stephen Rothwell
2014-03-19  0:53 Stephen Rothwell
2014-03-19  0:53 ` Stephen Rothwell
2014-03-19  1:18 ` Steven Rostedt
2014-03-19  1:18   ` Steven Rostedt
2013-02-15  2:37 Stephen Rothwell
2013-02-15  2:37 ` Stephen Rothwell
2013-02-15  9:30 ` Daniel Vetter
2013-02-15  9:30   ` Daniel Vetter
2013-02-15 16:16   ` Jesse Barnes
2013-02-19  2:01     ` Stephen Rothwell
2013-02-19 10:28       ` 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=87ed8hbele.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mitulkumar.ajitkumar.golani@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=sfr@canb.auug.org.au \
    --cc=suraj.kandpal@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.