All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Pavel Machek <pavel@kernel.org>,
	linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@linaro.org>,
	kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] leds: aw200xx: don't use return with gpiod_set_value() variants
Date: Wed, 12 Feb 2025 15:55:12 +0000	[thread overview]
Message-ID: <20250212155512.GE2274105@google.com> (raw)
In-Reply-To: <CAMRc=MdFwe2onYhwY__n-kAOSrXKKDWJ38hpbYb0711Nx60DHw@mail.gmail.com>

On Wed, 12 Feb 2025, Bartosz Golaszewski wrote:

> On Wed, Feb 12, 2025 at 9:59 AM Bartosz Golaszewski <brgl@bgdev.pl> wrote:
> >
> > From: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> >
> > While it now returns void, it will soon be converted to return an
> > integer instead. Don't do `return gpiod_set...`.
> >
> > Reported-by: kernel test robot <lkp@intel.com>
> > Closes: https://lore.kernel.org/oe-kbuild-all/202502121512.CmoMg9Q7-lkp@intel.com/
> > Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
> > ---
> >  drivers/leds/leds-aw200xx.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/leds/leds-aw200xx.c b/drivers/leds/leds-aw200xx.c
> > index 08cca128458c..fe223d363a5d 100644
> > --- a/drivers/leds/leds-aw200xx.c
> > +++ b/drivers/leds/leds-aw200xx.c
> > @@ -379,7 +379,7 @@ static void aw200xx_enable(const struct aw200xx *const chip)
> >
> >  static void aw200xx_disable(const struct aw200xx *const chip)
> >  {
> > -       return gpiod_set_value_cansleep(chip->hwen, 0);
> > +       gpiod_set_value_cansleep(chip->hwen, 0);
> >  }
> >
> >  static int aw200xx_probe_get_display_rows(struct device *dev,
> > --
> > 2.45.2
> >
> 
> Lee, Pavel:
> 
> If this is OK for you, can you please provide me with an immutable
> branch so that I can pull it into the GPIO tree? It seems it's the
> only such use-case in the tree apart from the gpio.h header that I can
> fix locally. Alternatively you can just Ack this and let me take it
> through the GPIO tree.

I'm okay with it, but why do you need it?

-- 
Lee Jones [李琼斯]

  reply	other threads:[~2025-02-12 15:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-12  8:59 [PATCH] leds: aw200xx: don't use return with gpiod_set_value() variants Bartosz Golaszewski
2025-02-12  9:02 ` Bartosz Golaszewski
2025-02-12 15:55   ` Lee Jones [this message]
2025-02-12 16:39     ` Bartosz Golaszewski
2025-02-17 10:44       ` Bartosz Golaszewski
2025-02-20 15:19 ` Lee Jones

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=20250212155512.GE2274105@google.com \
    --to=lee@kernel.org \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=brgl@bgdev.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=pavel@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 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.