linux-kernel - Re: [PATCH v2] usb: typec: hd3ss3220: Enable VBUS based on role state

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: <29eedf1f-7dcd-497d-a569-488d7cfb69c9@phytec.de>
Date: Mon, 26 Jan 2026 10:32:40 +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: Enable VBUS based on role state

Am 26.01.26 um 10:05 schrieb Greg Kroah-Hartman:
> On Mon, Jan 26, 2026 at 08:04:58AM +0000, Jan Remmet wrote:
>> Am 23.01.26 um 17:19 schrieb Greg Kroah-Hartman:
>>> Does not apply against my tree, what did you make it against?  Can you
>>> redo this against linux-next and resend?
>>
>> This is strange. I created it against 944aacb68baf (something after
>> v6.19-rc5). I can cleanly rebase it to next-20260123 without changes.
>> Do I miss something?
> 
> Probably other changes to this file since then?  linux-next will include
> the USB development tree that has the work of everyone else in it that
> will go into the next release.

I saw on usb-next my v1 is already applied. After removing it, it 
applies well. Sorry for the late change on this patch.

Jan
> 
> Try rebasing and see what happens :)
> 
> thanks,
> 
> greg k-h