From: Michal Wilczynski <m.wilczynski@samsung.com>
To: "Stephen Rothwell" <sfr@canb.auug.org.au>,
"Uwe Kleine-König" <ukleinek@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the pwm tree
Date: Tue, 28 Oct 2025 10:52:20 +0100 [thread overview]
Message-ID: <5748e9f5-b560-467b-a50d-5590b9acbaf1@samsung.com> (raw)
In-Reply-To: <20251028133924.30a058af@canb.auug.org.au>
On 10/28/25 03:39, Stephen Rothwell wrote:
> Hi all,
>
> After merging the pwm tree, today's linux-next build (x86_64 allmodconfig)
> produced these warnings:
>
> WARNING: modpost: module pwm_th1520 uses symbol pwmchip_release from namespace PWM, but does not import it.
> WARNING: modpost: module pwm_th1520 uses symbol __pwmchip_add from namespace PWM, but does not import it.
> WARNING: modpost: module pwm_th1520 uses symbol pwmchip_alloc from namespace PWM, but does not import it.
> WARNING: modpost: module pwm_th1520 uses symbol pwmchip_remove from namespace PWM, but does not import it.
Hi, Thank you for the report. Interestingly this seems to be the first
Rust driver that needs to write 'import_ns' in the .modpost section. For
C drivers the macro MODULE_IMPORT_NS("PWM") was simply included with
pwm.h. I think the module! macro needs to be extended to support
import_ns in rust/macros/module.rs. I think I know how to do it code
wise, will post a patch.
>
> Presumably introduced by commit
>
> fb3957af9ec6 ("pwm: Add Rust driver for T-HEAD TH1520 SoC")
>
Best regards,
--
Michal Wilczynski <m.wilczynski@samsung.com>
next prev parent reply other threads:[~2025-10-28 9:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20251028023933eucas1p1ea7f8b51a5da190b593635cea7e72982@eucas1p1.samsung.com>
2025-10-28 2:39 ` Stephen Rothwell
2025-10-28 9:52 ` Michal Wilczynski [this message]
2024-10-01 3:52 Stephen Rothwell
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=5748e9f5-b560-467b-a50d-5590b9acbaf1@samsung.com \
--to=m.wilczynski@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=ukleinek@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
all inboxes | Powered by JetHome®