linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Shawn Guo <shawnguo@kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Anson Huang <anson.huang@nxp.com>,
	Dong Aisheng <aisheng.dong@nxp.com>
Subject: linux-next: build failure after merge of the imx-mxs tree
Date: Tue, 21 May 2019 08:37:56 +1000	[thread overview]
Message-ID: <20190521083756.4c8aee8a@canb.auug.org.au> (raw)

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

Hi Shawn,

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

drivers/clk/imx/clk.c: In function 'imx_mmdc_mask_handshake':
drivers/clk/imx/clk.c:20:8: error: implicit declaration of function 'readl_relaxed'; did you mean 'xchg_relaxed'? [-Werror=implicit-function-declaration]
  reg = readl_relaxed(ccm_base + CCM_CCDR);
        ^~~~~~~~~~~~~
        xchg_relaxed
drivers/clk/imx/clk.c:22:2: error: implicit declaration of function 'writel_relaxed'; did you mean 'xchg_relaxed'? [-Werror=implicit-function-declaration]
  writel_relaxed(reg, ccm_base + CCM_CCDR);
  ^~~~~~~~~~~~~~
  xchg_relaxed

Caused by commit

  0dc6b492b6e0 ("clk: imx: Add common API for masking MMDC handshake")

I have used the imx-mxs tree from next-20190520 for today.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2019-05-20 22:37 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-20 22:37 Stephen Rothwell [this message]
2019-05-21  2:16 ` linux-next: build failure after merge of the imx-mxs tree Anson Huang
2019-05-21  4:43   ` Shawn Guo
  -- strict thread matches above, loose matches on Subject: below --
2023-03-07  1:31 Stephen Rothwell
2022-10-30 22:09 Stephen Rothwell
2022-10-30 22:11 ` Alistair
2022-10-31  0:52   ` Shawn Guo
2021-12-06 22:10 Stephen Rothwell
2021-12-07  7:27 ` Michal Vokáč
2020-11-03  1:00 Stephen Rothwell
2020-11-03  6:39 ` Shawn Guo
2020-02-18  2:08 Stephen Rothwell
2020-02-18  2:18 ` Peng Fan
2020-02-18  9:38   ` Shawn Guo
2019-12-11 21:35 Stephen Rothwell
2019-12-12  1:33 ` Shawn Guo
2019-12-12  9:45   ` Lucas Stach
2019-12-12 11:37     ` Shawn Guo
2019-04-22 22:45 Stephen Rothwell
2019-04-22 22:54 ` Fabio Estevam
2019-04-23  2:12 ` Shawn Guo
2019-01-10 22:30 Stephen Rothwell
2019-01-10 22:56 ` Stephen Rothwell
2019-01-10 23:15   ` Lukasz Majewski
2019-01-12  1:23     ` Shawn Guo
2015-06-01 12:35 Stephen Rothwell
2015-05-29 11:28 Stephen Rothwell
2015-05-29 13:16 ` Shawn Guo

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=20190521083756.4c8aee8a@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=aisheng.dong@nxp.com \
    --cc=anson.huang@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).