[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231011135905.hveat7viflqluccw@bogus>
Date: Wed, 11 Oct 2023 14:59:05 +0100
From: Sudeep Holla <sudeep.holla@....com>
To: Arnd Bergmann <arnd@...nel.org>
Cc: Rob Herring <robh+dt@...nel.org>,
Frank Rowand <frowand.list@...il.com>,
Sudeep Holla <sudeep.holla@....com>,
Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Yang Yang <yang.yang29@....com>,
Geert Uytterhoeven <geert+renesas@...der.be>,
Sebastian Reichel <sre@...nel.org>,
Miquel Raynal <miquel.raynal@...tlin.com>,
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>,
Viresh Kumar <viresh.kumar@...aro.org>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] of: rexport of_find_next_cache_node()
On Wed, Oct 11, 2023 at 03:14:08PM +0200, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@...db.de>
>
> This function is now called from a cpufreq driver, but that breaks the
> build when the caller is in a loadable module, because of a missing
> export:
>
> ERROR: modpost: "of_find_next_cache_node" [drivers/cpufreq/qcom-cpufreq-nvmem.ko] undefined!
>
> Export this as a GPL-only symbol, like the other related functions in
> this file.
>
> Fixes: 7683a63c08ff5 ("cpufreq: qcom-nvmem: create L2 cache device")
> Fixes: a3e31b4588443 ("of: Move definition of of_find_next_cache_node into common code.")
I am bit confused as I see commit a3e31b4588443 didn't drop the export.
So how is this change fixing that commit ?
--
Regards,
Sudeep
Powered by blists - more mailing lists