From: Lee Jones <lee@kernel.org>
To: "William Breathitt Gray" <william.gray@linaro.org>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Lee Jones" <lee@kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Biju Das" <biju.das.jz@bp.renesas.com>,
"Arnd Bergmann" <arnd@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Peter Robinson <pbrobinson@gmail.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pwm@vger.kernel.org
Subject: Re: (subset) [PATCH] mfd: rz-mtu3: link time dependencies
Date: Fri, 28 Jul 2023 11:57:06 +0100 [thread overview]
Message-ID: <169054182650.337347.17531123476992287995.b4-ty@kernel.org> (raw)
In-Reply-To: <20230719090430.1925182-1-arnd@kernel.org>
On Wed, 19 Jul 2023 11:02:23 +0200, Arnd Bergmann wrote:
> The new set of drivers for RZ/G2L MTU3a tries to enable compile-testing the
> individual client drivers even when the MFD portion is disabled but gets it
> wrong, causing a link failure when the core is in a loadable module but the
> other drivers are built-in:
>
> x86_64-linux-ld: drivers/pwm/pwm-rz-mtu3.o: in function `rz_mtu3_pwm_apply':
> pwm-rz-mtu3.c:(.text+0x4bf): undefined reference to `rz_mtu3_8bit_ch_write'
> x86_64-linux-ld: pwm-rz-mtu3.c:(.text+0x509): undefined reference to `rz_mtu3_disable'
>
> [...]
Applied, thanks!
[1/1] mfd: rz-mtu3: link time dependencies
commit: 36a676ed76ae1f8dedbb093e1db1662458e00b6a
--
Lee Jones [李琼斯]
prev parent reply other threads:[~2023-07-28 10:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 9:02 [PATCH] mfd: rz-mtu3: link time dependencies Arnd Bergmann
2023-07-19 9:11 ` Biju Das
2023-07-20 15:00 ` Thierry Reding
2023-07-21 8:00 ` Lee Jones
2023-07-21 12:20 ` Thierry Reding
2023-07-28 10:57 ` Lee Jones [this message]
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=169054182650.337347.17531123476992287995.b4-ty@kernel.org \
--to=lee@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=pbrobinson@gmail.com \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=william.gray@linaro.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