From: Jacky Bai <ping.bai@nxp.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, Abel Vesa <abel.vesa@nxp.com>
Cc: Peng Fan <peng.fan@nxp.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: RE: linux-next: build failure after merge of the clk-imx tree
Date: Fri, 17 Sep 2021 00:47:36 +0000 [thread overview]
Message-ID: <DBBPR04MB79301D1C70ED0E6FB04151DA87DD9@DBBPR04MB7930.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20210917090618.3a7ac4be@canb.auug.org.au>
> Subject: linux-next: build failure after merge of the clk-imx tree
>
> Hi all,
>
> After merging the clk-imx tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> ERROR: modpost: "imx_clk_hw_pfdv2" [drivers/clk/imx/clk-imx8ulp.ko]
> undefined!
> ERROR: modpost: "imx_clk_hw_pllv4" [drivers/clk/imx/clk-imx8ulp.ko]
> undefined!
> ERROR: modpost: "imx8ulp_clk_hw_composite" [drivers/clk/imx/clk-imx8ulp.ko]
> undefined!
>
should because that these three functions are not export symbol when driver build as module.
I will generate a patch to fix it.
Thx for reporting this issue.
BR
Jacky Bai
> Caused by commit
>
> 86ce2d393ff7 ("clk: imx: Add clock driver for imx8ulp")
>
> I have used the clk-imx tree from next-20210916 fot today.
>
> --
> Cheers,
> Stephen Rothwell
next prev parent reply other threads:[~2021-09-17 0:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 23:06 Stephen Rothwell
2021-09-17 0:47 ` Jacky Bai [this message]
2021-09-17 8:21 ` Abel Vesa
2022-09-05 23:34 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=DBBPR04MB79301D1C70ED0E6FB04151DA87DD9@DBBPR04MB7930.eurprd04.prod.outlook.com \
--to=ping.bai@nxp.com \
--cc=abel.vesa@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®