From: Sven Schwermer <sven@svenschwermer.de>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "Linux LED Subsystem" <linux-leds@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
linux-pwm@vger.kernel.org,
"Sven Schwermer" <sven.schwermer@disruptive-technologies.com>,
"Pavel Machek" <pavel@ucw.cz>, "Rob Herring" <robh+dt@kernel.org>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Lee Jones" <lee.jones@linaro.org>,
post@lespocky.de
Subject: Re: [PATCH v3 2/2] leds: Add PWM multicolor driver
Date: Sun, 6 Feb 2022 10:17:51 +0100 [thread overview]
Message-ID: <20f95cfd-a851-af4f-1c60-45f2ca238e10@svenschwermer.de> (raw)
In-Reply-To: <CAHp75VfMTCvgib__PhnfB_g7xLhyNws5TDRyMVyzuAkT1ydY_w@mail.gmail.com>
Hi Andy,
Thanks for looking through my patch. I have a couple of follow-up
questions about your feedback:
On 2/2/22 13:33, Andy Shevchenko wrote:
>> + ret = PTR_ERR(pwmled->pwm);
>> + dev_err(&pdev->dev, "unable to request PWM: %d\n", ret);
>> + fwnode_handle_put(fwnode);
>> + goto destroy_mutex;
>
> fwnode_handle_put();
> return dev_err_probe(...);
This would skip the destruction of the mutex and releasing of mcnode.
Isn't that problematic? The same goes for all of your comments of this kind.
>> +destroy_mutex:
>> + mutex_destroy(&priv->lock);
>
> Wrong ordering here and in ->remove().
>
> Don't mix devm_* with non-devm_* calls.
What do you mean by this?
Best regards,
Sven
next prev parent reply other threads:[~2022-02-06 9:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 10:48 [PATCH v3 0/2] Multicolor PWM LED support sven
2022-01-26 10:48 ` [PATCH v3 1/2] dt-bindings: leds: Add multicolor PWM LED bindings sven
2022-01-27 21:24 ` Jacek Anaszewski
2022-01-28 20:36 ` Marek Behún
2022-01-28 23:04 ` Jacek Anaszewski
2022-01-28 23:26 ` Marek Behún
2022-01-31 7:10 ` Alexander Dahl
2022-01-31 8:55 ` Sven Schwermer
2022-02-12 11:54 ` Pavel Machek
2022-01-26 10:48 ` [PATCH v3 2/2] leds: Add PWM multicolor driver sven
2022-02-02 12:33 ` Andy Shevchenko
2022-02-06 9:17 ` Sven Schwermer [this message]
[not found] ` <CAHp75VeSD5bYERp=s9Dzd0xScVc+sYSdc8W4XBfCVXJgyWMPyA@mail.gmail.com>
2022-02-06 11:04 ` Sven Schwermer
2022-02-06 12:25 ` Andy Shevchenko
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=20f95cfd-a851-af4f-1c60-45f2ca238e10@svenschwermer.de \
--to=sven@svenschwermer.de \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=post@lespocky.de \
--cc=robh+dt@kernel.org \
--cc=sven.schwermer@disruptive-technologies.com \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.