From: Alexander Dahl <post@lespocky.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Alexander Dahl" <ada@thorsis.com>,
"Alexander Dahl" <post@lespocky.de>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
"Jacek Anaszewski" <jacek.anaszewski@gmail.com>,
"Dan Murphy" <dmurphy@ti.com>, "Rob Herring" <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org,
"Peter Ujfalusi" <peter.ujfalusi@ti.com>,
"Marek Behún" <marek.behun@nic.cz>,
"Denis Osterland-Heim" <denis.osterland@diehl.com>
Subject: Re: [PATCH v5 1/3] leds: pwm: Remove platform_data support
Date: Thu, 1 Oct 2020 00:57:58 +0200 [thread overview]
Message-ID: <20200930225757.wqz5x4th5ywfeduv@falbala.internal.home.lespocky.de> (raw)
In-Reply-To: <20200930172441.GI27760@duo.ucw.cz>
[-- Attachment #1: Type: text/plain, Size: 1952 bytes --]
Hello Pavel,
On Wed, Sep 30, 2020 at 07:24:41PM +0200, Pavel Machek wrote:
> Hi!
>
> > > > +__attribute__((nonnull))
> > > >
> > > > static int led_pwm_add(struct device *dev, struct led_pwm_priv *priv,
> > > >
> > > > struct led_pwm *led, struct fwnode_handle *fwnode)
> > > >
> > > > {
> > >
> > > This normally goes elsewhere -- right? I'd expect:
> > >
> > >
> > > static int led_pwm_add(struct device *dev, struct led_pwm_priv *priv,
> > > struct led_pwm *led, struct fwnode_handle *fwnode)
> > > __attribute__((nonnull))
> >
> > I found both variants in kernel code. I can live with both variants and have
> > no strong preference.
> >
> > My initial intention to add it was to get a compiler warning in case someone
> > does not pass a fwnode here, e.g. when using that old platform_data approach
> > (which is supposed to be removed with this patch). You might call it a self
> > check on my own changes. I can also drop that attribute if you don't want
> > that kind of stuff in linux-leds.
>
> I'm okay with it at the second place :-).
Should have tried this before, but I actually did now. O:-)
If I move the attribute behind, I get this on a W=1 build:
CC drivers/leds/leds-pwm.o
/home/alex/src/linux/leds/drivers/leds/leds-pwm.c:58:1: error: attributes should be specified before the declarator in a function definition
static int led_pwm_add(struct device *dev, struct led_pwm_priv *priv,
^~~~~~
Because it won't build then, I'll keep it where it is. Meanwhile I
worked on all the DT remarks by Rob and I will send v6 soon.
Greets
Alex
--
/"\ ASCII RIBBON | »With the first link, the chain is forged. The first
\ / CAMPAIGN | speech censured, the first thought forbidden, the
X AGAINST | first freedom denied, chains us all irrevocably.«
/ \ HTML MAIL | (Jean-Luc Picard, quoting Judge Aaron Satie)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-09-30 22:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-19 5:31 [PATCH v5 0/3] leds: pwm: Make automatic labels work Alexander Dahl
2020-09-19 5:31 ` [PATCH v5 1/3] leds: pwm: Remove platform_data support Alexander Dahl
2020-09-19 9:44 ` Pavel Machek
2020-09-28 11:04 ` Alexander Dahl
2020-09-30 17:24 ` Pavel Machek
2020-09-30 22:57 ` Alexander Dahl [this message]
2020-09-19 18:05 ` Marek Behun
2020-09-19 5:31 ` [PATCH v5 2/3] leds: pwm: Allow automatic labels for DT based devices Alexander Dahl
2020-09-19 9:44 ` Pavel Machek
2020-09-19 5:31 ` [PATCH v5 3/3] dt-bindings: leds: Convert pwm to yaml Alexander Dahl
2020-09-22 15:42 ` Rob Herring
2020-09-28 11:19 ` Alexander Dahl
2020-09-28 16:11 ` Rob Herring
2020-09-22 15:57 ` Rob Herring
2020-09-29 7:39 ` Alexander Dahl
2020-09-29 13:58 ` Rob Herring
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=20200930225757.wqz5x4th5ywfeduv@falbala.internal.home.lespocky.de \
--to=post@lespocky.de \
--cc=ada@thorsis.com \
--cc=denis.osterland@diehl.com \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=jacek.anaszewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=marek.behun@nic.cz \
--cc=pavel@ucw.cz \
--cc=peter.ujfalusi@ti.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).