From: Yixun Lan <dlan@gentoo.org>
To: Inochi Amaoto <inochiama@gmail.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Haylen Chu <heylenay@4d2.org>,
Brian Masney <bmasney@redhat.com>,
Troy Mitchell <troy.mitchell@linux.spacemit.com>,
Alex Elder <elder@riscstar.com>,
Akhilesh Patil <akhilesh@ee.iitb.ac.in>,
linux-clk@vger.kernel.org, linux-riscv@lists.infradead.org,
spacemit@lists.linux.dev, linux-kernel@vger.kernel.org,
Longbin Li <looong.bin@gmail.com>
Subject: Re: [PATCH] clk: spacemit: Fix module build for spacemit common ccu driver
Date: Tue, 16 Dec 2025 06:12:02 +0800 [thread overview]
Message-ID: <20251215221202-GYA1903981@gentoo.org> (raw)
In-Reply-To: <20251214232938.668293-1-inochiama@gmail.com>
Hi Inochi,
On 07:29 Mon 15 Dec , Inochi Amaoto wrote:
> For build spacemit common clock driver as a module, the build
> process require MODULE_LICENSE()/MODULE_DESCRIPTION() globally
> and EXPORT_SYMBOL() for every exposed symbol. Otherwise, the
> build will fail.
>
> Add these missing hints, so the driver can be built as a module.
>
> Fixes: 1b72c59db0ad ("clk: spacemit: Add clock support for SpacemiT K1 SoC")
> Signed-off-by: Inochi Amaoto <inochiama@gmail.com>
looks good, thanks
Reviewed-by: Yixun Lan <dlan@gentoo.org>
--
Yixun Lan (dlan)
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-12-15 22:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-14 23:29 [PATCH] clk: spacemit: Fix module build for spacemit common ccu driver Inochi Amaoto
2025-12-15 2:54 ` Troy Mitchell
2025-12-15 22:18 ` Yixun Lan
2025-12-15 22:12 ` Yixun Lan [this message]
2025-12-16 14:48 ` Yixun Lan
2025-12-16 22:47 ` Inochi Amaoto
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=20251215221202-GYA1903981@gentoo.org \
--to=dlan@gentoo.org \
--cc=akhilesh@ee.iitb.ac.in \
--cc=bmasney@redhat.com \
--cc=elder@riscstar.com \
--cc=heylenay@4d2.org \
--cc=inochiama@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=looong.bin@gmail.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=spacemit@lists.linux.dev \
--cc=troy.mitchell@linux.spacemit.com \
/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