From: Marc Kleine-Budde <mkl@pengutronix.de>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, linux-can@vger.kernel.org,
kernel@pengutronix.de, Marc Kleine-Budde <mkl@pengutronix.de>,
kernel test robot <lkp@intel.com>,
Pavel Pisa <pisa@cmp.felk.cvut.cz>,
Ondrej Ille <ondrej.ille@gmail.com>
Subject: [PATCH net-next 3/3] can: ctucanfd: platform: add missing dependency to HAS_IOMEM
Date: Mon, 23 May 2022 22:10:45 +0200 [thread overview]
Message-ID: <20220523201045.1708855-4-mkl@pengutronix.de> (raw)
In-Reply-To: <20220523201045.1708855-1-mkl@pengutronix.de>
The kernel test robot noticed that the ctucanfd platform driver fails
during modpost on platforms that don't support IOMEM.
| ERROR: modpost: "devm_ioremap_resource" [drivers/net/can/ctucanfd/ctucanfd_platform.ko] undefined!
This patch adds the missing HAS_IOMEM dependency.
Link: https://lore.kernel.org/all/20220523123720.1656611-1-mkl@pengutronix.de
Fixes: e8f0c23a2415 ("can: ctucanfd: CTU CAN FD open-source IP core - platform/SoC support.")
Reported-by: kernel test robot <lkp@intel.com>
Acked-by: Pavel Pisa <pisa@cmp.felk.cvut.cz>
Cc: Ondrej Ille <ondrej.ille@gmail.com>
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
---
drivers/net/can/ctucanfd/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/can/ctucanfd/Kconfig b/drivers/net/can/ctucanfd/Kconfig
index 3c383612eb17..6e2073351a8f 100644
--- a/drivers/net/can/ctucanfd/Kconfig
+++ b/drivers/net/can/ctucanfd/Kconfig
@@ -23,7 +23,7 @@ config CAN_CTUCANFD_PCI
config CAN_CTUCANFD_PLATFORM
tristate "CTU CAN-FD IP core platform (FPGA, SoC) driver"
- depends on OF || COMPILE_TEST
+ depends on HAS_IOMEM && (OF || COMPILE_TEST)
select CAN_CTUCANFD
help
The core has been tested together with OpenCores SJA1000
--
2.35.1
next prev parent reply other threads:[~2022-05-23 20:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 20:10 [PATCH net-next 0/3] pull-request: can-next 2022-05-23 Marc Kleine-Budde
2022-05-23 20:10 ` [PATCH net-next 1/3] can: peak_usb: fix typo in comment Marc Kleine-Budde
2022-05-23 23:10 ` patchwork-bot+netdevbpf
2022-05-23 20:10 ` [PATCH net-next 2/3] can: kvaser_usb: silence a GCC 12 -Warray-bounds warning Marc Kleine-Budde
2022-05-23 20:10 ` Marc Kleine-Budde [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-05-23 20:08 [PATCH net-next 0/n] pull-request: can-next 2022-05-23 Marc Kleine-Budde
2022-05-23 20:08 ` [PATCH net-next 3/3] can: ctucanfd: platform: add missing dependency to HAS_IOMEM Marc Kleine-Budde
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=20220523201045.1708855-4-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=ondrej.ille@gmail.com \
--cc=pisa@cmp.felk.cvut.cz \
/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).