linux-kernel - Re: (subset) [PATCH v2 01/15] leds: aw200xx: don't use return with gpiod_set

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250313152921.GB3645863@google.com>
Date: Thu, 13 Mar 2025 15:29:21 +0000
From: Lee Jones <lee@...nel.org>
To: Bartosz Golaszewski <brgl@...ev.pl>
Cc: Linus Walleij <linus.walleij@...aro.org>,
	Michael Walle <mwalle@...nel.org>,
	Bamvor Jian Zhang <bamv2005@...il.com>,
	Geert Uytterhoeven <geert+renesas@...der.be>,
	Keerthy <j-keerthy@...com>,
	Uwe Kleine-König <ukleinek@...nel.org>,
	linux-gpio@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-pwm@...r.kernel.org,
	Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
	Pavel Machek <pavel@...nel.org>, linux-leds@...r.kernel.org,
	kernel test robot <lkp@...el.com>
Subject: Re: (subset) [PATCH v2 01/15] leds: aw200xx: don't use return with
 gpiod_set_value() variants

On Fri, 07 Mar 2025, Bartosz Golaszewski wrote:

> On Thu, Mar 6, 2025 at 11:51 PM Lee Jones <lee@...nel.org> wrote:
> >
> > On Thu, 20 Feb 2025 10:56:58 +0100, Bartosz Golaszewski wrote:
> > > While gpiod_set_value() currently returns void, it will soon be converted
> > > to return an integer instead. Don't do `return gpiod_set...`.
> > >
> > >
> >
> > Applied, thanks!
> >
> > [01/15] leds: aw200xx: don't use return with gpiod_set_value() variants
> >         commit: 5d5e2a6f15a6c5e0c431c1388fd90e14b448da1e
> >
> 
> Hi Lee!
> 
> Can you please drop it from your tree? You acked v1 of this patch
> after I had already sent v2 (this patch remained unchanged) folded
> into a respin of the bigger GPIO series that had triggered build bots
> to point this issue out in the first place. I picked the entire series
> up and this commit is already in next as
> 129fdfe25ac513018d5fe85b0c493025193ef19f.

Unapplied, thanks.

-- 
Lee Jones [李琼斯]