From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jan Remmet <J.Remmet@phytec.de>
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: Enable VBUS based on role state
Date: Mon, 26 Jan 2026 11:42:02 +0100 [thread overview]
Message-ID: <2026012639-gag-sufferer-a344@gregkh> (raw)
In-Reply-To: <29eedf1f-7dcd-497d-a569-488d7cfb69c9@phytec.de>
On Mon, Jan 26, 2026 at 10:32:40AM +0000, Jan Remmet wrote:
> 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.
I can't remove a patch from the tree, if there is something different
here, please send a new "fix up" patch for that.
thanks,
greg k-h
prev parent reply other threads:[~2026-01-26 10:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 14:52 [PATCH v2] usb: typec: hd3ss3220: Enable VBUS based on role state Jan Remmet
2026-01-23 16:19 ` Greg Kroah-Hartman
2026-01-26 8:04 ` Jan Remmet
2026-01-26 9:05 ` Greg Kroah-Hartman
2026-01-26 10:32 ` Jan Remmet
2026-01-26 10:42 ` Greg Kroah-Hartman [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=2026012639-gag-sufferer-a344@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=J.Remmet@phytec.de \
--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