From: Anson Huang <anson.huang@nxp.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Shawn Guo <shawnguo@kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Aisheng Dong <aisheng.dong@nxp.com>
Subject: RE: linux-next: build failure after merge of the imx-mxs tree
Date: Tue, 21 May 2019 02:16:47 +0000 [thread overview]
Message-ID: <DB3PR0402MB39165C5944880EA0B0A37F91F5070@DB3PR0402MB3916.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20190521083756.4c8aee8a@canb.auug.org.au>
Hi, Stephen/Shawn
I realized this issue last week when I updated my Linux-next tree (NOT sure why I did NOT meet such issue when I did the patch), so I resent the patch series of adding head file "io.h" to fix this issue, please apply below V2 patch series instead, sorry for the inconvenience.
https://patchwork.kernel.org/patch/10944681/
thanks,
Anson.
> -----Original Message-----
> From: Stephen Rothwell [mailto:sfr@canb.auug.org.au]
> Sent: Tuesday, May 21, 2019 6:38 AM
> 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>;
> Aisheng Dong <aisheng.dong@nxp.com>
> Subject: linux-next: build failure after merge of the imx-mxs tree
>
> 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
next prev parent reply other threads:[~2019-05-21 2:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 22:37 linux-next: build failure after merge of the imx-mxs tree Stephen Rothwell
2019-05-21 2:16 ` Anson Huang [this message]
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=DB3PR0402MB39165C5944880EA0B0A37F91F5070@DB3PR0402MB3916.eurprd04.prod.outlook.com \
--to=anson.huang@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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).