public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kevin Hilman <khilman@baylibre.com>, Carlo Caione <carlo@caione.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jianxin Pan <jianxin.pan@amlogic.com>
Subject: linux-next: build failure after merge of the amlogic tree
Date: Mon, 17 Feb 2020 08:25:59 +1100	[thread overview]
Message-ID: <20200217082559.73e736d2@canb.auug.org.au> (raw)

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

Hi all,

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

arm-linux-gnueabi-ld: drivers/soc/amlogic/meson-secure-pwrc.o: in function `pwrc_secure_is_off':
meson-secure-pwrc.c:(.text+0x4c): undefined reference to `meson_sm_call'
arm-linux-gnueabi-ld: drivers/soc/amlogic/meson-secure-pwrc.o: in function `meson_secure_pwrc_off':
meson-secure-pwrc.c:(.text+0xc8): undefined reference to `meson_sm_call'
arm-linux-gnueabi-ld: drivers/soc/amlogic/meson-secure-pwrc.o: in function `meson_secure_pwrc_on':
meson-secure-pwrc.c:(.text+0x128): undefined reference to `meson_sm_call'
arm-linux-gnueabi-ld: drivers/soc/amlogic/meson-secure-pwrc.o: in function `meson_secure_pwrc_probe':
meson-secure-pwrc.c:(.text+0x1ac): undefined reference to `meson_sm_get'

Caused by commit

  b3dde5013e13 ("soc: amlogic: Add support for Secure power domains controller")

I have used the amloginc tree from next-20200214 for today.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2020-02-16 21:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-16 21:25 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-06-05 23:55 linux-next: build failure after merge of the amlogic tree Stephen Rothwell
2016-06-06  3:40 ` Kevin Hilman
2016-06-06  4:02   ` Stephen Rothwell
2016-06-09 22:43     ` Kevin Hilman

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=20200217082559.73e736d2@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=carlo@caione.org \
    --cc=jianxin.pan@amlogic.com \
    --cc=khilman@baylibre.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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