From: Vincent Mailhol <mailhol@kernel.org>
To: Marc Kleine-Budde <mkl@pengutronix.de>,
Arnd Bergmann <arnd@arndb.de>,
Oliver Hartkopp <socketcan@hartkopp.net>
Cc: kernel@pengutronix.de, linux-can@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH can] can: fix build dependency
Date: Wed, 17 Dec 2025 23:24:05 +0100 [thread overview]
Message-ID: <f188b330-8bf5-4509-a2fc-712c20160167@kernel.org> (raw)
In-Reply-To: <20251217-can-fix-dependency-v1-1-fd2d4f2a2bf5@pengutronix.de>
On 17/12/2025 at 10:45, Marc Kleine-Budde wrote:
> Arnd Bergmann's patch [1] fixed the build dependency problem introduced by
> bugfix commit cb2dc6d2869a ("can: Kconfig: select CAN driver infrastructure
> by default"). This ended up as commit 6abd4577bccc ("can: fix build
> dependency"), but I broke Arnd's fix by removing a dependency that we
> thought was superfluous.
And my comment subverted you into doing so. I think half of the blame goes to me
here.
> [1] https://lore.kernel.org/all/20251204100015.1033688-1-arnd@kernel.org/
>
> Meanwhile the problem was also found by intel's kernel test robot,
> complaining about undefined symbols:
>
> | ERROR: modpost: "m_can_class_unregister" [drivers/net/can/m_can/m_can_platform.ko] undefined!
> | ERROR: modpost: "m_can_class_free_dev" [drivers/net/can/m_can/m_can_platform.ko] undefined!
> | ERROR: modpost: "m_can_class_allocate_dev" [drivers/net/can/m_can/m_can_platform.ko] undefined!
> | ERROR: modpost: "m_can_class_get_clocks" [drivers/net/can/m_can/m_can_platform.ko] undefined!
> | ERROR: modpost: "m_can_class_register" [drivers/net/can/m_can/m_can_platform.ko] undefined!
>
> To fix this problem, add the missing dependency again.
>
> Cc: Vincent Mailhol <mailhol@kernel.org>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202512132253.vO9WFDJK-lkp@intel.com/
> Reported-by: Arnd Bergmann <arnd@arndb.de>
> Closes: https://lore.kernel.org/all/7427949a-ea7d-4854-9fe4-e01db7d878c7@app.fastmail.com/
> Fixes: 6abd4577bccc ("can: fix build dependency")
> Fixes: cb2dc6d2869a ("can: Kconfig: select CAN driver infrastructure by default")
> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
Acked-by: Vincent Mailhol <mailhol@kernel.org>
Yours sincerely,
Vincent Mailhol
next prev parent reply other threads:[~2025-12-17 22:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 9:45 Marc Kleine-Budde
2025-12-17 22:24 ` Vincent Mailhol [this message]
2025-12-18 12:32 ` 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=f188b330-8bf5-4509-a2fc-712c20160167@kernel.org \
--to=mailhol@kernel.org \
--cc=arnd@arndb.de \
--cc=kernel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mkl@pengutronix.de \
--cc=socketcan@hartkopp.net \
/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®