[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8b77219e-b59e-40f1-96f1-980a0b2debcf@infradead.org>
Date: Tue, 12 Sep 2023 15:28:29 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-clk@...r.kernel.org, dl-linux-imx <linux-imx@....com>,
Abel Vesa <abelvesa@...nel.org>, Peng Fan <peng.fan@....com>
Subject: Re: linux-next: Tree for Sep 12 (drivers/clk/imx/clk-imx8-acm.o)
On 9/11/23 22:26, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20230911:
>
> New tree: bcachefs
>
> The bcachefs tree gained a semantic conflict against Linus' tree for
> which I applied a patch.
>
> The wireless-next tree gaind a conflict against the wireless tree.
>
> Non-merge commits (relative to Linus' tree): 4095
> 1552 files changed, 346893 insertions(+), 22945 deletions(-)
>
> ----------------------------------------------------------------------------
on arm64:
aarch64-linux-ld: drivers/clk/imx/clk-imx8-acm.o: in function `imx8_acm_clk_probe':
clk-imx8-acm.c:(.text+0x3d0): undefined reference to `imx_check_clk_hws'
when
CONFIG_CLK_IMX8QXP=y
CONFIG_MXC_CLK=m
Should CLK_IMX8QXP select MXC_CLK?
I'll leave that patch up to the maintainers.
Reported-by: Randy Dunlap <rdunlap@...radead.org>
--
~Randy
Powered by blists - more mailing lists