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: <f203856efd3deedce56cc39dda13d563636c5f7e.camel@pengutronix.de>
Date: Thu, 08 Jan 2026 13:02:09 +0100
From: Philipp Zabel <p.zabel@...gutronix.de>
To: Bartosz Golaszewski <brgl@...nel.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>, 
	linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org, Bartosz
 Golaszewski	 <bartosz.golaszewski@...aro.org>, Bartosz Golaszewski
 <brgl@...ev.pl>
Subject: Re: [PATCH] reset: gpio: add the "compatible" property

Hi Bartosz,

On Mo, 2025-12-08 at 23:57 -0800, Bartosz Golaszewski wrote:
> On Tue, 25 Nov 2025 11:43:01 +0100, Philipp Zabel <p.zabel@...gutronix.de> said:
> > On Fr, 2025-11-21 at 14:57 +0100, Bartosz Golaszewski wrote:
> > > From: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
> > > 
> > > In order to correctly handle the interaction between the reset-gpio
> > > devices and shared GPIOs managed by GPIOLIB, we need to be able to
> > > identify the former. Add the "compatible" property to allow us to use
> > > the device_is_compatible() helper.
> > > 
> > > Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@...aro.org>
> > > ---
> > > Philipp: this can go directly into your branch, I will fix the GPIO part
> > > in the next cycle. For now it just parses the device name.
> > 
> > Applied to reset/next, thanks!
> > 
> > [1/1] reset: gpio: add the "compatible" property
> >       https://git.pengutronix.de/cgit/pza/linux/commit/?id=a0d57f7504b6
> > 
> > regards
> > Philipp
> > 
> 
> Hi Phillipp!
> 
> I realized this didn't make your v6.19-rc1 PR. Any chance you could make it
> into an immutable branch or maybe you could back it out from your branch and
> allow me to take it with your Ack? I have a WiP patch that fixes one remaining
> issue in the interaction between reset-gpios and shared GPIOs. I want to send
> it for rc1 or rc2 but I would prefer to use device_is_compatible() in it.

Sorry for the delay, I didn't get to this before hibernating. I've now
rebased the patch onto v6.19-rc1 now and made an immutable branch for
you to fetch:

The following changes since commit 8f0b4cce4481fb22653697cced8d0d04027cb1e8:

  Linux 6.19-rc1 (2025-12-14 16:05:07 +1200)

are available in the Git repository at:

  https://git.pengutronix.de/git/pza/linux.git reset/gpio-compatible

for you to fetch changes up to b3d8508351af7f6366a0a18068c194b399ead2c3:

  reset: gpio: add the "compatible" property (2026-01-08 12:25:20 +0100)

----------------------------------------------------------------
Bartosz Golaszewski (1):
      reset: gpio: add the "compatible" property

 drivers/reset/core.c | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

regards
Philipp

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ