From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Rob Clark <robdclark@gmail.com>, Sean Paul <seanpaul@chromium.org>
Cc: 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-msm tree
Date: Wed, 23 Jun 2021 11:02:05 +1000 [thread overview]
Message-ID: <20210623110205.05f98019@canb.auug.org.au> (raw)
In-Reply-To: <20210618125019.4a339135@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 783 bytes --]
Hi all,
On Fri, 18 Jun 2021 12:50:19 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> [Adding maintainers]
>
> On Fri, 18 Jun 2021 12:42:03 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > After merging the etnaviv tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
> >
> > ERROR: modpost: "__aeabi_ldivmod" [drivers/gpu/drm/msm/msm.ko] undefined!
> > ERROR: modpost: "__aeabi_uldivmod" [drivers/gpu/drm/msm/msm.ko] undefined!
> >
> > I don't know which commit in the drm-msm tree caused the failure, but
> > it is probably in the range 558d4272b60f..7e0230fd096c.
> >
> > I have used the drm-msm tree from next-20210617 for today.
I am still seeing this (as of yesterday).
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-06-23 1:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 2:42 linux-next: build failure after merge of the drm-msm tree Stephen Rothwell
2021-06-18 2:50 ` Stephen Rothwell
2021-06-23 1:02 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-11 0:59 Stephen Rothwell
2023-10-10 1:54 Stephen Rothwell
2022-05-05 1:48 Stephen Rothwell
2022-05-05 1:43 Stephen Rothwell
2021-07-29 11:28 Mark Brown
2018-10-05 1:37 Stephen Rothwell
2018-07-23 4:50 Stephen Rothwell
2018-07-25 12:08 ` Rob Clark
2018-06-04 3:20 Stephen Rothwell
2016-07-11 3:20 Stephen Rothwell
2015-12-15 1:27 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=20210623110205.05f98019@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=seanpaul@chromium.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