Linux-Next discussions
 help / color / mirror / Atom feed
From: Ran Bi <ran.bi@mediatek.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the rtc tree
Date: Mon, 16 Mar 2020 14:58:42 +0800	[thread overview]
Message-ID: <1584341922.16860.5.camel@mhfsdcap03> (raw)
In-Reply-To: <20200316161558.438c7d8b@canb.auug.org.au>

Hi Belloni,

On Mon, 2020-03-16 at 16:15 +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the rtc tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
> 
> drivers/rtc/rtc-mt2712.c: In function 'mt2712_rtc_set_alarm':
> drivers/rtc/rtc-mt2712.c:235:6: warning: unused variable 'irqen' [-Wunused-variable]
>   235 |  u16 irqen;
>       |      ^~~~~
> drivers/rtc/rtc-mt2712.c: At top level:
> drivers/rtc/rtc-mt2712.c:409:1: error: expected ',' or ';' before 'static'
>   409 | static struct platform_driver mt2712_rtc_driver = {
>       | ^~~~~~
> In file included from drivers/rtc/rtc-mt2712.c:14:
> drivers/rtc/rtc-mt2712.c: In function 'mt2712_rtc_driver_init':
> drivers/rtc/rtc-mt2712.c:418:24: error: 'mt2712_rtc_driver' undeclared (first use in this function); did you mean 'mt2712_rtc_probe'?
>   418 | module_platform_driver(mt2712_rtc_driver);
>       |                        ^~~~~~~~~~~~~~~~~
> include/linux/platform_device.h:214:29: note: in definition of macro 'platform_driver_register'
>   214 |  __platform_driver_register(drv, THIS_MODULE)
>       |                             ^~~
> include/linux/platform_device.h:244:2: note: in expansion of macro 'module_driver'
>   244 |  module_driver(__platform_driver, platform_driver_register, \
>       |  ^~~~~~~~~~~~~
> drivers/rtc/rtc-mt2712.c:418:1: note: in expansion of macro 'module_platform_driver'
>   418 | module_platform_driver(mt2712_rtc_driver);
>       | ^~~~~~~~~~~~~~~~~~~~~~
> drivers/rtc/rtc-mt2712.c:418:24: note: each undeclared identifier is reported only once for each function it appears in
>   418 | module_platform_driver(mt2712_rtc_driver);
>       |                        ^~~~~~~~~~~~~~~~~
> include/linux/platform_device.h:214:29: note: in definition of macro 'platform_driver_register'
>   214 |  __platform_driver_register(drv, THIS_MODULE)
>       |                             ^~~
> include/linux/platform_device.h:244:2: note: in expansion of macro 'module_driver'
>   244 |  module_driver(__platform_driver, platform_driver_register, \
>       |  ^~~~~~~~~~~~~
> drivers/rtc/rtc-mt2712.c:418:1: note: in expansion of macro 'module_platform_driver'
>   418 | module_platform_driver(mt2712_rtc_driver);
>       | ^~~~~~~~~~~~~~~~~~~~~~
> In file included from include/linux/device.h:31,
>                  from include/linux/platform_device.h:13,
>                  from drivers/rtc/rtc-mt2712.c:14:
> drivers/rtc/rtc-mt2712.c: In function 'mt2712_rtc_driver_exit':
> drivers/rtc/rtc-mt2712.c:418:24: error: 'mt2712_rtc_driver' undeclared (first use in this function); did you mean 'mt2712_rtc_probe'?
>   418 | module_platform_driver(mt2712_rtc_driver);
>       |                        ^~~~~~~~~~~~~~~~~
> include/linux/device/driver.h:266:17: note: in definition of macro 'module_driver'
>   266 |  __unregister(&(__driver) , ##__VA_ARGS__); \
>       |                 ^~~~~~~~
> drivers/rtc/rtc-mt2712.c:418:1: note: in expansion of macro 'module_platform_driver'
>   418 | module_platform_driver(mt2712_rtc_driver);
>       | ^~~~~~~~~~~~~~~~~~~~~~
> drivers/rtc/rtc-mt2712.c: In function 'mt2712_rtc_driver_init':
> drivers/rtc/rtc-mt2712.c:418:1: warning: control reaches end of non-void function [-Wreturn-type]
>   418 | module_platform_driver(mt2712_rtc_driver);
>       | ^~~~~~~~~~~~~~~~~~~~~~
> At top level:
> drivers/rtc/rtc-mt2712.c:312:12: warning: 'mt2712_rtc_probe' defined but not used [-Wunused-function]
>   312 | static int mt2712_rtc_probe(struct platform_device *pdev)
>       |            ^~~~~~~~~~~~~~~~
> 
> Caused by commit
> 
>   00c36d73171b ("rtc: add support for the MediaTek MT2712 RTC")
> 
> I have used the version from next-20200313 for today.
> 

This build fail only happen if rtc-mt2712 build as module which I
haven't try. It because ";" was missed after "MODULE_DEVICE_TABLE(of,
mt2712_rtc_of_match)". Should I send a fix patch for this or resend the
whole rtc-mt2712 driver?

Regards,
Ran

  reply	other threads:[~2020-03-16  6:59 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-16  5:15 linux-next: build failure after merge of the rtc tree Stephen Rothwell
2020-03-16  6:58 ` Ran Bi [this message]
2020-03-16 10:31   ` Alexandre Belloni
  -- strict thread matches above, loose matches on Subject: below --
2024-11-13  5:23 Stephen Rothwell
2023-10-16  4:15 Stephen Rothwell
2023-10-16  4:34 ` Alexandre Belloni
2023-10-16  7:11 ` Uwe Kleine-König
2021-09-27  3:10 Stephen Rothwell
2021-09-27  7:16 ` Romain Perier
2021-08-10  5:54 Stephen Rothwell
2019-10-04  4:37 Stephen Rothwell
2019-02-11  5:24 Stephen Rothwell
2019-02-08  5:55 Stephen Rothwell
2017-05-31  4:33 Stephen Rothwell
2017-05-31  5:45 ` Heiner Kallweit
2017-05-31  7:19   ` Alexandre Belloni
2017-04-10  6:04 Stephen Rothwell
2017-04-10  7:45 ` Hans de Goede
2017-04-11  0:22   ` Stephen Rothwell
2017-04-11  5:55     ` Alexandre Belloni
2017-04-11  7:52       ` Stephen Rothwell
2017-04-14 10:09         ` Alexandre Belloni
2017-04-14 16:33           ` Stephen Rothwell
2016-11-08  6:41 Stephen Rothwell
2016-11-08 22:21 ` Alexandre Belloni
2015-12-17  5:03 Stephen Rothwell
2015-12-17 11:21 ` Alexandre Belloni
2015-12-18 15:30   ` Sasha Levin
2015-12-18 16:43     ` Alexandre Belloni
2015-12-22 19:27       ` Alexandre Belloni

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=1584341922.16860.5.camel@mhfsdcap03 \
    --to=ran.bi@mediatek.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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