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] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABTCjFDQoQcrkYwBhaH0bzdxHd6OsGh1J+iFqme5R3HfLdeq3g@mail.gmail.com>
Date: Thu, 17 Jul 2025 17:36:45 +0300
From: Dzmitry Sankouski <dsankouski@...il.com>
To: Ivaylo Ivanov <ivo.ivanov.ivanov1@...il.com>
Cc: Krzysztof Kozlowski <krzk@...nel.org>, Lee Jones <lee@...nel.org>, Rob Herring <robh@...nel.org>, 
	Conor Dooley <conor+dt@...nel.org>, Liam Girdwood <lgirdwood@...il.com>, 
	Mark Brown <broonie@...nel.org>, linux-kernel@...r.kernel.org, 
	linux-samsung-soc@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v5 3/3] regulator: add s2dos05 regulator support

чт, 17 июл. 2025 г. в 14:33, Ivaylo Ivanov <ivo.ivanov.ivanov1@...il.com>:
>
> On 7/17/25 11:12, Dzmitry Sankouski wrote:
> > чт, 17 июл. 2025 г. в 10:28, Ivaylo Ivanov <ivo.ivanov.ivanov1@...il.com>:
> >> On 9/26/24 12:47, Dzmitry Sankouski wrote:
> >>> S2DOS05 has 1 buck and 4 LDO regulators, used for powering
> >>> panel/touchscreen.
> >>>
> >>> Signed-off-by: Dzmitry Sankouski <dsankouski@...il.com>
> >> When is this going to get merged? This patch brings the regulators
> >> functionality of the pmic, so not having it merged is odd. This PMIC is
> >> used on other devices too, like the Galaxy S22.
> >>
> >> It seems like this has been hanging for almost an year at this point.
> >> If the author won't, will somebody resend it?
> >
> > It's already merged, see
> > https://lore.kernel.org/all/20240617-starqltechn_integration_upstream-v5-2-ea1109029ba5@gmail.com/
>
> I don't see patch 3/3 being merged anywhere, nor is it in my linux-next clone
> from today. Do you _not_ need it anymore?
>

Indeed, that commit is not present, that's strange. I'll reset that patch later.

-- 

Best regards,
Dzmitry

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ