All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Rob Clark <robdclark@gmail.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Sharat Masetty <smasetty@codeaurora.org>
Subject: linux-next: build failure after merge of the drm-msm tree
Date: Fri, 5 Oct 2018 11:37:38 +1000	[thread overview]
Message-ID: <20181005113738.2b7e4e1d@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 455 bytes --]

Hi Rob,

After merging the drm-msm tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:

arm-linux-gnueabi-ld: drivers/gpu/drm/msm/adreno/a6xx_gpu.o: in function `a6xx_gpu_busy':
a6xx_gpu.c:(.text+0x70): undefined reference to `__aeabi_uldivmod'

Caused by commit

  a2c3c0a54d4c ("drm/msm/a6xx: Add devfreq support for a6xx")

I have used the drm-msm tree from next-20181004 for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2018-10-05  1:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-05  1:37 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-11  0:59 linux-next: build failure after merge of the drm-msm tree Stephen Rothwell
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:48 ` Stephen Rothwell
2022-05-05  1:43 Stephen Rothwell
2022-05-05  1:43 ` Stephen Rothwell
2021-07-29 11:28 Mark Brown
2021-06-18  2:42 Stephen Rothwell
2021-06-18  2:50 ` Stephen Rothwell
2021-06-23  1:02   ` Stephen Rothwell
2018-07-23  4:50 Stephen Rothwell
2018-07-23  4:50 ` Stephen Rothwell
2018-07-25 12:08 ` Rob Clark
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=20181005113738.2b7e4e1d@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=smasetty@codeaurora.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 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.