From: Jan Remmet <J.Remmet@phytec.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"upstream@lists.phytec.de" <upstream@lists.phytec.de>
Subject: Re: [PATCH v2] usb: typec: hd3ss3220: Check if regulator needs to be switched
Date: Thu, 5 Feb 2026 19:37:29 +0000 [thread overview]
Message-ID: <0424ffd8-4872-4c2f-8315-2d9064a0a477@phytec.de> (raw)
In-Reply-To: <2026020520-confider-selector-0b67@gregkh>
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
prev parent reply other threads:[~2026-02-05 19:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 14:42 [PATCH v2] usb: typec: hd3ss3220: Check if regulator needs to be switched Jan Remmet
2026-01-27 15:10 ` Greg Kroah-Hartman
2026-01-30 8:57 ` Jan Remmet
2026-02-05 16:18 ` Greg Kroah-Hartman
2026-02-05 19:37 ` Jan Remmet [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0424ffd8-4872-4c2f-8315-2d9064a0a477@phytec.de \
--to=j.remmet@phytec.de \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=krishna.kurapati@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=upstream@lists.phytec.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox