From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Gene Chen <gene.chen.richtek@gmail.com>,
pavel@ucw.cz, robh+dt@kernel.org, matthias.bgg@gmail.com
Cc: dmurphy@ti.com, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
gene_chen@richtek.com, Wilma.Wu@mediatek.com,
shufan_lee@richtek.com, cy_huang@richtek.com,
benjamin.chao@mediatek.com
Subject: Re: [PATCH v9 2/6] leds: flash: Fix multicolor registration no-ops by return 0
Date: Thu, 26 Nov 2020 19:14:14 +0100 [thread overview]
Message-ID: <a4670d78-18c9-37e5-d984-5aab1a5635f1@gmail.com> (raw)
In-Reply-To: <1606390654-6075-3-git-send-email-gene.chen.richtek@gmail.com>
Hi Gene,
On 11/26/20 12:37 PM, Gene Chen wrote:
> From: Gene Chen <gene_chen@richtek.com>
>
> Fix multicolor registration no-ops by return 0
>
> Signed-off-by: Gene Chen <gene_chen@richtek.com>
> ---
> include/linux/led-class-multicolor.h | 42 +++++++++++++-----------------------
> 1 file changed, 15 insertions(+), 27 deletions(-)
>
> diff --git a/include/linux/led-class-multicolor.h b/include/linux/led-class-multicolor.h
> index 5116f9a..210d57b 100644
> --- a/include/linux/led-class-multicolor.h
> +++ b/include/linux/led-class-multicolor.h
> @@ -44,12 +44,6 @@ int led_classdev_multicolor_register_ext(struct device *parent,
> struct led_classdev_mc *mcled_cdev,
> struct led_init_data *init_data);
>
> -static inline int led_classdev_multicolor_register(struct device *parent,
> - struct led_classdev_mc *mcled_cdev)
> -{
> - return led_classdev_multicolor_register_ext(parent, mcled_cdev, NULL);
> -}
> -
> /**
> * led_classdev_multicolor_unregister - unregisters an object of led_classdev
> * class with support for multicolor LEDs
> @@ -68,13 +62,6 @@ int devm_led_classdev_multicolor_register_ext(struct device *parent,
> struct led_classdev_mc *mcled_cdev,
> struct led_init_data *init_data);
>
> -static inline int devm_led_classdev_multicolor_register(struct device *parent,
> - struct led_classdev_mc *mcled_cdev)
> -{
> - return devm_led_classdev_multicolor_register_ext(parent, mcled_cdev,
> - NULL);
> -}
> -
> void devm_led_classdev_multicolor_unregister(struct device *parent,
> struct led_classdev_mc *mcled_cdev);
> #else
> @@ -83,27 +70,33 @@ static inline int led_classdev_multicolor_register_ext(struct device *parent,
> struct led_classdev_mc *mcled_cdev,
> struct led_init_data *init_data)
> {
> - return -EINVAL;
> -}
> -
> -static inline int led_classdev_multicolor_register(struct device *parent,
> - struct led_classdev_mc *mcled_cdev)
> -{
> - return led_classdev_multicolor_register_ext(parent, mcled_cdev, NULL);
> + return 0;
> }
>
> static inline void led_classdev_multicolor_unregister(struct led_classdev_mc *mcled_cdev) {};
> static inline int led_mc_calc_color_components(struct led_classdev_mc *mcled_cdev,
> enum led_brightness brightness)
> {
> - return -EINVAL;
> + return 0;
> }
>
> static inline int devm_led_classdev_multicolor_register_ext(struct device *parent,
> struct led_classdev_mc *mcled_cdev,
> struct led_init_data *init_data)
> {
> - return -EINVAL;
> + return 0;
> +}
> +
> +static inline void devm_led_classdev_multicolor_unregister(struct device *parent,
> + struct led_classdev_mc *mcled_cdev)
> +{};
> +
> +#endif /* IS_ENABLED(CONFIG_LEDS_CLASS_MULTICOLOR) */
> +
> +static inline int led_classdev_multicolor_register(struct device *parent,
> + struct led_classdev_mc *mcled_cdev)
> +{
> + return led_classdev_multicolor_register_ext(parent, mcled_cdev, NULL);
> }
>
> static inline int devm_led_classdev_multicolor_register(struct device *parent,
> @@ -113,9 +106,4 @@ static inline int devm_led_classdev_multicolor_register(struct device *parent,
> NULL);
> }
>
> -static inline void devm_led_classdev_multicolor_unregister(struct device *parent,
> - struct led_classdev_mc *mcled_cdev)
> -{};
> -
> -#endif /* IS_ENABLED(CONFIG_LEDS_CLASS_MULTICOLOR) */
> #endif /* _LINUX_MULTICOLOR_LEDS_H_INCLUDED */
>
Here the same comment as for the patch 1/6.
With that:
Acked-by: Jacek Anaszewski <jacek.anaszewski@gmail.com>
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2020-11-26 18:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 11:37 [PATCH v9 0/6] leds: mt6360: Add LED driver for MT6360 Gene Chen
2020-11-26 11:37 ` [PATCH v9 1/6] leds: flash: Add flash registration with undefined CONFIG_LEDS_CLASS_FLASH Gene Chen
2020-11-26 18:12 ` Jacek Anaszewski
2020-11-26 11:37 ` [PATCH v9 2/6] leds: flash: Fix multicolor registration no-ops by return 0 Gene Chen
2020-11-26 18:14 ` Jacek Anaszewski [this message]
2020-11-26 11:37 ` [PATCH v9 3/6] dt-bindings: leds: Add LED_FUNCTION_MOONLIGHT definitions Gene Chen
2020-11-26 11:37 ` [PATCH v9 4/6] dt-bindings: leds: common: Increase LED_COLOR_ID_* maximum size Gene Chen
2020-11-26 11:37 ` [PATCH v9 5/6] dt-bindings: leds: Add bindings for MT6360 LED Gene Chen
2020-11-26 11:37 ` [PATCH v9 6/6] leds: mt6360: Add LED driver for MT6360 Gene Chen
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=a4670d78-18c9-37e5-d984-5aab1a5635f1@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=Wilma.Wu@mediatek.com \
--cc=benjamin.chao@mediatek.com \
--cc=cy_huang@richtek.com \
--cc=devicetree@vger.kernel.org \
--cc=dmurphy@ti.com \
--cc=gene.chen.richtek@gmail.com \
--cc=gene_chen@richtek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=shufan_lee@richtek.com \
/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).