All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Reichel <sebastian.reichel@collabora.com>
To: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
Cc: Marek Vasut <marex@nabladev.com>,
	linux-usb@vger.kernel.org,  stable@vger.kernel.org,
	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: Mon, 24 Aug 2026 14:18:46 +0200	[thread overview]
Message-ID: <aow2jLtrvHqPLI_w@venus> (raw)
In-Reply-To: <ef89a8ba-af41-425a-90e5-77061fec3f9f@oldschoolsolutions.biz>

[-- Attachment #1: Type: text/plain, Size: 762 bytes --]

Hi,

On Sat, Aug 22, 2026 at 09:47:33AM +0200, Jens Glathe wrote:
> 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>

Thanks!

-- Sebastian

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2026-08-24 12:19 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
2026-08-24 12:18   ` Sebastian Reichel [this message]
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=aow2jLtrvHqPLI_w@venus \
    --to=sebastian.reichel@collabora.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=marex@nabladev.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 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.