From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: AceLan Kao <acelan.kao@canonical.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Pooja Katiyar <pooja.katiyar@intel.com>,
Abel Vesa <abel.vesa@linaro.org>,
Andrei Kuchynski <akuchynski@chromium.org>,
Venkat Jayaraman <venkat.jayaraman@intel.com>,
"Christian A. Ehrhardt" <lk@c--e.de>,
Pei Xiao <xiaopei01@kylinos.cn>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] usb: typec: ucsi: Detect and skip duplicate altmodes from buggy firmware
Date: Wed, 11 Feb 2026 10:43:12 +0200 [thread overview]
Message-ID: <aYxBIIkztIkuVSiu@kuha> (raw)
In-Reply-To: <2026021133-mystify-division-2468@gregkh>
Hi,
On Wed, Feb 11, 2026 at 06:36:50AM +0100, Greg Kroah-Hartman wrote:
> On Wed, Feb 11, 2026 at 11:32:37AM +0800, AceLan Kao wrote:
> > A gentle ping.
> > Please help to review these patches, thanks.
I'm sorry, but I don't seem to have this thread (probable because of
our spam filter). This reply from Greg is the first mail I can see.
This is a Dell platform, right? Did anyone contact Dell about this?
thanks,
> It is the middle of the merge window, nothing can happen until after
> -rc1 is out, you know this :(
--
heikki
next prev parent reply other threads:[~2026-02-11 8:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 7:00 [PATCH v3 1/3] usb: typec: ucsi: Detect and skip duplicate altmodes from buggy firmware Chia-Lin Kao (AceLan)
2025-12-24 7:00 ` [PATCH v3 2/3] usb: typec: ucsi: Add duplicate detection to nvidia registration path Chia-Lin Kao (AceLan)
2025-12-24 7:00 ` [PATCH v3 3/3] usb: typec: ucsi: yoga_c630: Remove redundant duplicate altmode handling Chia-Lin Kao (AceLan)
2026-02-11 3:32 ` [PATCH v3 1/3] usb: typec: ucsi: Detect and skip duplicate altmodes from buggy firmware AceLan Kao
2026-02-11 5:36 ` Greg Kroah-Hartman
2026-02-11 8:43 ` Heikki Krogerus [this message]
2026-02-11 5:37 ` Greg Kroah-Hartman
2026-03-05 14:58 ` Dmitry Baryshkov
2026-03-11 13:57 ` Heikki Krogerus
2026-04-08 10:09 ` Heikki Krogerus
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=aYxBIIkztIkuVSiu@kuha \
--to=heikki.krogerus@linux.intel.com \
--cc=abel.vesa@linaro.org \
--cc=acelan.kao@canonical.com \
--cc=akuchynski@chromium.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lk@c--e.de \
--cc=pooja.katiyar@intel.com \
--cc=venkat.jayaraman@intel.com \
--cc=xiaopei01@kylinos.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.