linux-kernel - Re: [PATCH v2] usb: typec: hd3ss3220: Check if regulator needs to be switched

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: <0424ffd8-4872-4c2f-8315-2d9064a0a477@phytec.de>
Date: Thu, 5 Feb 2026 19:37:29 +0000
From: Jan Remmet <J.Remmet@...tec.de>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC: Heikki Krogerus <heikki.krogerus@...ux.intel.com>, Krishna Kurapati
	<krishna.kurapati@....qualcomm.com>, "linux-usb@...r.kernel.org"
	<linux-usb@...r.kernel.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, "upstream@...ts.phytec.de"
	<upstream@...ts.phytec.de>
Subject: Re: [PATCH v2] usb: typec: hd3ss3220: Check if regulator needs to be
 switched

Am 05.02.26 um 17:18 schrieb Greg Kroah-Hartman:
> On Tue, Jan 27, 2026 at 03:42:15PM +0100, Jan Remmet wrote:
>> Check regulator state as peripheral and detach can disable vbus.
>> Without this check we will try to disable the regulator twice if
>> we disconnect host and then connect as device.
>>
>> Fixes: 7e7025811579 ("usb: typec: hd3ss3220: Check if regulator needs to be switched")
> 
> This is not a git id in the tree :(
> 
> And how can this "fix" the same commit that this one is?
> 
> Totally confused...
Sorry, I mixed it up :(
I accidentally took the last reference, which was the actual commit...
> 
> How about starting over and picking the commit id, in the tree, that
> this is fixing and sending that?

Yes, I already send v3 with fixed reference.

https://lore.kernel.org/all/20260127-wip-jremmet-hd3ss3220_vbus_split-v3-1-009772f38265@phytec.de/

Jan
> 
> thanks,
> 
> greg k-h