From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Horatiu Vultur <horatiu.vultur@microchip.com>,
<linux-kernel@vger.kernel.org>, <linux-clk@vger.kernel.org>
Cc: <mturquette@baylibre.com>, <sboyd@kernel.org>,
<kavyasree.kotagiri@microchip.com>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] clk: lan966x: Fix linking error
Date: Mon, 21 Feb 2022 17:43:37 +0100 [thread overview]
Message-ID: <994b754f-a8b0-2504-0803-d12fa9975ff5@microchip.com> (raw)
In-Reply-To: <20220219141536.460812-1-horatiu.vultur@microchip.com>
On 19/02/2022 at 15:15, Horatiu Vultur wrote:
> If the config options HAS_IOMEM is not set then the driver fails to link
> with the following error:
> clk-lan966x.c:(.text+0x950): undefined reference to
> `devm_platform_ioremap_resource'
>
> Therefor add missing dependencies: HAS_IOMEM and OF.
>
> Fixes: 54104ee02333 ("clk: lan966x: Add lan966x SoC clock driver")
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
Reviewed-by: Nicolas Ferre <nicolas.ferre@microchip.com>
> ---
> drivers/clk/Kconfig | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/clk/Kconfig b/drivers/clk/Kconfig
> index 4a8451f61f37..6f03c29c40be 100644
> --- a/drivers/clk/Kconfig
> +++ b/drivers/clk/Kconfig
> @@ -232,6 +232,8 @@ config COMMON_CLK_GEMINI
>
> config COMMON_CLK_LAN966X
> bool "Generic Clock Controller driver for LAN966X SoC"
> + depends on HAS_IOMEM
> + depends on OF
> help
> This driver provides support for Generic Clock Controller(GCK) on
> LAN966X SoC. GCK generates and supplies clock to various peripherals
--
Nicolas Ferre
next prev parent reply other threads:[~2022-02-21 16:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-19 14:15 [PATCH] clk: lan966x: Fix linking error Horatiu Vultur
2022-02-21 16:43 ` Nicolas Ferre [this message]
2022-02-25 0:53 ` Stephen Boyd
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=994b754f-a8b0-2504-0803-d12fa9975ff5@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=horatiu.vultur@microchip.com \
--cc=kavyasree.kotagiri@microchip.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@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