linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Georgi Djakov <georgi.djakov@linaro.org>
Subject: linux-next: build failure after merge of the opp tree
Date: Thu, 14 May 2020 11:58:11 +1000	[thread overview]
Message-ID: <20200514115811.1c6192b5@canb.auug.org.au> (raw)

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

Hi all,

After merging the opp tree, today's linux-next build (x86_64 allmodconfig)
failed like this:

x86_64-linux-gnu-ld: drivers/opp/core.o: in function `dev_pm_opp_put_opp_table':
(.text+0x76e): undefined reference to `icc_put'
x86_64-linux-gnu-ld: drivers/opp/core.o: in function `dev_pm_opp_set_rate':
(.text+0x2c59): undefined reference to `icc_set_bw'
x86_64-linux-gnu-ld: drivers/opp/of.o: in function `dev_pm_opp_of_find_icc_paths':
(.text+0x3ca): undefined reference to `of_icc_get_by_index'
x86_64-linux-gnu-ld: (.text+0x441): undefined reference to `icc_set_tag'
x86_64-linux-gnu-ld: (.text+0x542): undefined reference to `icc_put'

Caused by commit

  12fa389dcf86 ("OPP: Add support for parsing interconnect bandwidth")

I have used the opp tree from next-20200512 for today.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2020-05-14  1:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-14  1:58 Stephen Rothwell [this message]
2020-05-14  6:38 ` linux-next: build failure after merge of the opp tree Viresh Kumar

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=20200514115811.1c6192b5@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=georgi.djakov@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).