From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Jani Nikula <jani.nikula@linux.intel.com>,
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: Mon, 17 Jun 2024 15:19:44 -0400 [thread overview]
Message-ID: <ZnCMUEd9dQ6bLNet@intel.com> (raw)
In-Reply-To: <20240612141239.141ce8cc@canb.auug.org.au>
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.
>
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2024-06-17 19:20 UTC|newest]
Thread overview: 36+ 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 [this message]
2024-06-27 21:48 ` Dave Airlie
2024-06-28 9:29 ` Jani Nikula
-- strict thread matches above, loose matches on Subject: below --
2024-08-29 3:46 Stephen Rothwell
2022-08-26 2:36 Stephen Rothwell
2022-08-26 7:50 ` Jani Nikula
2022-04-26 2:08 Stephen Rothwell
2022-04-26 7:36 ` Jani Nikula
2022-02-15 1:10 Stephen Rothwell
2022-02-15 12:11 ` Jani Nikula
2021-05-21 1:58 Stephen Rothwell
2021-01-19 23:57 Stephen Rothwell
2021-01-21 1:11 ` Stephen Rothwell
[not found] <20191210093957.5120f717@canb.auug.org.au>
[not found] ` <20191210094224.4a294cb7@canb.auug.org.au>
2019-12-11 9:31 ` Jani Nikula
2019-03-27 2:59 Stephen Rothwell
2019-03-27 11:07 ` Joonas Lahtinen
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-09 5:02 ` Stephen Rothwell
2018-05-09 5:08 ` Christoph Hellwig
2018-05-09 5:18 ` Stephen Rothwell
2016-08-23 1:56 Stephen Rothwell
2016-08-23 16:33 ` Daniel Vetter
2016-05-23 2:24 Stephen Rothwell
2014-04-03 1:24 Stephen Rothwell
2014-03-19 0:53 Stephen Rothwell
2014-03-19 1:18 ` Steven Rostedt
2013-02-15 2:37 Stephen Rothwell
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=ZnCMUEd9dQ6bLNet@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--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=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 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).