mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kenneth Crudup <kenny@panix.com>
To: Jameson Thies <jthies@google.com>,
	heikki.krogerus@linux.intel.com, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org, Kenneth C <kenny@panix.com>
Cc: dmitry.baryshkov@oss.qualcomm.com, bleung@chromium.org,
	gregkh@linuxfoundation.org, akuchynski@chromium.org,
	abhishekpandit@chromium.org, sebastian.reichel@collabora.com,
	linux-pm@vger.kernel.org
Subject: Re: [PATCH v2 0/3] UCSI Power Supply Updates
Date: Thu, 16 Oct 2025 17:16:15 -0700	[thread overview]
Message-ID: <7f969633-6a5c-4694-a33e-b7d4d975ce59@panix.com> (raw)
In-Reply-To: <20251016235909.2092917-1-jthies@google.com>


On 10/16/25 16:59, Jameson Thies wrote:

> v2 changes
> - Removed patch adding support for reporting DRP power supply types.
>    It led to spam in dmesg and needs further debug.

So far, so good! I'm currently booted (along with the "Add power supply 
status" patch) and no issues so far.

I'll look for the sysfs entries and report back with a Tested-By: if all 
is well.

-Kenny--
Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange 
County CA


  parent reply	other threads:[~2025-10-17  0:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-16 23:59 Jameson Thies
2025-10-16 23:59 ` [PATCH v2 1/3] usb: typec: ucsi: psy: Add power supply status Jameson Thies
2025-10-17  0:09   ` Benson Leung
2025-10-16 23:59 ` [PATCH v2 2/3] usb: typec: ucsi: Report power supply changes on power opmode changes Jameson Thies
2025-10-16 23:59 ` [PATCH v2 3/3] usb: typec: ucsi: Report power supply change on sink path change Jameson Thies
2025-10-17  0:11   ` Benson Leung
2025-10-17  0:16 ` Kenneth Crudup [this message]
2025-10-17  0:25 ` [PATCH v2 0/3] UCSI Power Supply Updates Kenneth Crudup

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=7f969633-6a5c-4694-a33e-b7d4d975ce59@panix.com \
    --to=kenny@panix.com \
    --cc=abhishekpandit@chromium.org \
    --cc=akuchynski@chromium.org \
    --cc=bleung@chromium.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=jthies@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sebastian.reichel@collabora.com \
    /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

all inboxes | Powered by JetHome®