From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Joshua Kinard <kumba@gentoo.org>
Cc: linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/8] rtc: ds1685: fix build error with make W=1
Date: Tue, 26 Nov 2019 22:16:29 +0100 [thread overview]
Message-ID: <20191126211629.GP299836@piout.net> (raw)
In-Reply-To: <bee6cf44-a3e5-f217-388c-47165f1d5f90@gentoo.org>
On 23/11/2019 00:19:45-0500, Joshua Kinard wrote:
> On 11/22/2019 05:22, Alexandre Belloni wrote:
> > Fix the following parsing errors when building with W=1:
> > drivers/rtc/rtc-ds1685.c:1053: error: Cannot parse struct or union!
> > drivers/rtc/rtc-ds1685.c:1062: error: Cannot parse struct or union!
> > drivers/rtc/rtc-ds1685.c:1363: warning: cannot understand function prototype: 'struct platform_driver ds1685_rtc_driver = '
> >
> > Cc: Joshua Kinard <kumba@gentoo.org>
> > Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
> > ---
> > drivers/rtc/rtc-ds1685.c | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/rtc/rtc-ds1685.c b/drivers/rtc/rtc-ds1685.c
> > index 8419595e7da7..56c670af2e50 100644
> > --- a/drivers/rtc/rtc-ds1685.c
> > +++ b/drivers/rtc/rtc-ds1685.c
> > @@ -1039,7 +1039,7 @@ ds1685_rtc_sysfs_serial_show(struct device *dev,
> > }
> > static DEVICE_ATTR(serial, S_IRUGO, ds1685_rtc_sysfs_serial_show, NULL);
> >
> > -/**
> > +/*
> > * struct ds1685_rtc_sysfs_misc_attrs - list for misc RTC features.
> > */
> > static struct attribute*
> > @@ -1050,7 +1050,7 @@ ds1685_rtc_sysfs_misc_attrs[] = {
> > NULL,
> > };
> >
> > -/**
> > +/*
> > * struct ds1685_rtc_sysfs_misc_grp - attr group for misc RTC features.
> > */
> > static const struct attribute_group
> > @@ -1355,7 +1355,7 @@ ds1685_rtc_remove(struct platform_device *pdev)
> > return 0;
> > }
> >
> > -/**
> > +/*
> > * ds1685_rtc_driver - rtc driver properties.
> > */
> > static struct platform_driver ds1685_rtc_driver = {
> >
>
> /** is for kerneldoc comments. Is this a bug in kbuild's W=1 implementation
> of not parsing kerneldoc on a struct correctly? I'm sure I got that syntax
> for structs out of the kerneldoc guide, unless it changed at some point.
>
I would think it is gcc that is choking on that, probably because the
members are not described.
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-11-26 21:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 10:22 [PATCH 0/8] rtc: fix W=1 warnings and errors Alexandre Belloni
2019-11-22 10:22 ` [PATCH 1/8] rtc: sysfs: fix hctosys_show kerneldoc Alexandre Belloni
2019-11-22 10:22 ` [PATCH 2/8] rtc: ds1374: remove unused variable Alexandre Belloni
2019-11-22 10:22 ` [PATCH 3/8] rtc: ds1685: remove set but unused variables Alexandre Belloni
2019-11-23 5:16 ` Joshua Kinard
2019-11-22 10:22 ` [PATCH 4/8] rtc: ds1685: fix build error with make W=1 Alexandre Belloni
2019-11-23 5:19 ` Joshua Kinard
2019-11-26 21:16 ` Alexandre Belloni [this message]
2019-11-22 10:22 ` [PATCH 5/8] rtc: m41t80: remove excess kerneldoc Alexandre Belloni
2019-11-22 10:22 ` [PATCH 6/8] rtc: pm8xxx: update kerneldoc for struct pm8xxx_rtc Alexandre Belloni
2019-11-22 10:22 ` [PATCH 7/8] rtc: tegra: remove set but unused variable Alexandre Belloni
2019-11-22 12:46 ` Thierry Reding
2019-11-22 10:22 ` [PATCH 8/8] rtc: v3020: " 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=20191126211629.GP299836@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=kumba@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.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