From: Marek Vasut <marex@nabladev.com>
To: Jens Glathe <jens.glathe@oldschoolsolutions.biz>,
linux-usb@vger.kernel.org
Cc: stable@vger.kernel.org,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
kernel@dh-electronics.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: typec: mux: avoid duplicated mux switches
Date: Sat, 22 Aug 2026 10:06:31 +0200 [thread overview]
Message-ID: <472aba70-5216-46d0-8b9a-0a322d1d968e@nabladev.com> (raw)
In-Reply-To: <ef89a8ba-af41-425a-90e5-77061fec3f9f@oldschoolsolutions.biz>
On 8/22/26 9:47 AM, Jens Glathe wrote:
Hello Jens,
> On 8/22/26 09:24, Marek Vasut wrote:
>> This is a re-application of b145c3f29d62 ("usb: typec: mux: avoid
>> duplicated mux switches"), with fix derived from usb: typec: mux:
>> Fix typec_switch_match() .
>>
>> Fixes: f576c75f95a5 ("Revert "usb: typec: mux: avoid duplicated mux
>> switches"")
>> - Extensive test by Jens https://lore.kernel.org/
>> all/8bdf6062-8ec2-4c30-8463-0368d3a0f1ce@oldschoolsolutions.biz/
>>
> I applied both patches and compared to my tip of tree, same except for a
> newline. Also did a test on the Lenovo X13s (sc8280xp, gpio mux).
> Therefore justified:
>
> Tested-by: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
>
> with best regards
Thank you !
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2026-08-22 8:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-22 7:24 [PATCH] usb: typec: mux: avoid duplicated mux switches Marek Vasut
2026-08-22 7:47 ` Jens Glathe
2026-08-22 8:06 ` Marek Vasut [this message]
2026-08-24 12:18 ` Sebastian Reichel
2026-08-24 12:01 ` Heikki Krogerus
2026-08-24 12:30 ` Sebastian Reichel
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=472aba70-5216-46d0-8b9a-0a322d1d968e@nabladev.com \
--to=marex@nabladev.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jens.glathe@oldschoolsolutions.biz \
--cc=kernel@dh-electronics.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=stable@vger.kernel.org \
/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