From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Thierry Reding <thierry.reding@gmail•com>
Cc: "Linux Next Mailing List" <linux-next@vger•kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger•kernel.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix•de>,
"Mark Brown" <broonie@kernel•org>
Subject: Re: linux-next: build failure after merge of the pwm tree
Date: Sat, 12 Jan 2019 17:08:59 +1100 [thread overview]
Message-ID: <20190112170859.2cee77d0@canb.auug.org.au> (raw)
In-Reply-To: <20190112170117.0d4674fa@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
Hi all,
On Sat, 12 Jan 2019 17:01:17 +1100 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> [Reported by "kernelci.org bot" <bot@kernelci•org>]
[Also reported by Mark Brown <broonie@kernel•org>]
>
> After merging the pwm tree, today's linux-next build (arm64-allmodconfig)
> failed like this:
>
> In file included from drivers/pwm/pwm-imx27.c:15:
> drivers/pwm/pwm-imx27.c:292:25: error: 'imx_pwm_dt_ids' undeclared here (not in a function); did you mean 'pwm_imx27_dt_ids'?
> MODULE_DEVICE_TABLE(of, imx_pwm_dt_ids);
> ^~~~~~~~~~~~~~
> include/linux/module.h:213:15: note: in definition of macro 'MODULE_DEVICE_TABLE'
> extern typeof(name) __mod_##type##__##name##_device_table \
> ^~~~
> include/linux/module.h:213:21: error: '__mod_of__imx_pwm_dt_ids_device_table' aliased to undefined symbol 'imx_pwm_dt_ids'
> extern typeof(name) __mod_##type##__##name##_device_table \
> ^~~~~~
> drivers/pwm/pwm-imx27.c:292:1: note: in expansion of macro 'MODULE_DEVICE_TABLE'
> MODULE_DEVICE_TABLE(of, imx_pwm_dt_ids);
>
> Caused by commit
>
> 5a309d380019 ("pwm: imx: Split into two drivers")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-01-12 6:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-12 6:01 linux-next: build failure after merge of the pwm tree Stephen Rothwell
2019-01-12 6:08 ` Stephen Rothwell [this message]
2019-01-12 15:27 ` Uwe Kleine-König
[not found] <CGME20251027015241eucas1p1784b974d0c150e8c3513f32401205669@eucas1p1.samsung.com>
2025-10-27 1:51 ` Stephen Rothwell
2025-10-27 8:11 ` Uwe Kleine-König
2025-10-27 9:38 ` Danilo Krummrich
2025-10-28 1:51 ` Stephen Rothwell
2025-12-05 3:33 ` Stephen Rothwell
2025-10-27 13:40 ` Uwe Kleine-König
2025-10-27 13:49 ` Danilo Krummrich
2025-10-27 8:36 ` Michal Wilczynski
-- strict thread matches above, loose matches on Subject: below --
2023-12-21 5:58 Stephen Rothwell
2023-12-21 9:25 ` Thierry Reding
2023-12-21 10:09 ` Lee Jones
2023-12-21 12:13 ` Sean Young
2023-12-21 12:51 ` Lee Jones
2014-08-22 21:07 Stephen Rothwell
2014-08-22 22:06 ` Thierry Reding
2014-08-22 22:15 ` Thierry Reding
2014-08-22 22:30 ` 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=20190112170859.2cee77d0@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=broonie@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=thierry.reding@gmail$(echo .)com \
--cc=u.kleine-koenig@pengutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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