[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <173987422134.23672.3075019208527367982.b4-ty@linaro.org>
Date: Tue, 18 Feb 2025 11:23:46 +0100
From: Bartosz Golaszewski <brgl@...ev.pl>
To: Linus Walleij <linus.walleij@...aro.org>,
Bartosz Golaszewski <brgl@...ev.pl>
Cc: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
linux-gpio@...r.kernel.org,
linux-kernel@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: [PATCH v2] gpiolib: protect gpio_chip with SRCU in array_info paths in multi get/set
From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
On Sat, 15 Feb 2025 10:56:55 +0100, Bartosz Golaszewski wrote:
> During the locking rework in GPIOLIB, we omitted one important use-case,
> namely: setting and getting values for GPIO descriptor arrays with
> array_info present.
>
> This patch does two things: first it makes struct gpio_array store the
> address of the underlying GPIO device and not chip. Next: it protects
> the chip with SRCU from removal in gpiod_get_array_value_complex() and
> gpiod_set_array_value_complex().
>
> [...]
Applied, thanks!
[1/1] gpiolib: protect gpio_chip with SRCU in array_info paths in multi get/set
commit: 81570d6a7ad37033c7895811551a5a9023706eda
Best regards,
--
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
Powered by blists - more mailing lists