mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Matt DeVillier <matt.devillier@gmail.com>
Cc: Tzung-Bi Shih <tzungbi@kernel.org>,
	Sebastian Reichel <sre@kernel.org>,
	Benson Leung <bleung@chromium.org>,
	Guenter Roeck <groeck@chromium.org>,
	"open list:CHROMEOS EC SUBDRIVERS"
	<chrome-platform@lists.linux.dev>,
	"open list:POWER SUPPLY CLASS/SUBSYSTEM and DRIVERS"
	<linux-pm@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] power: supply: cros_charge-control: adopt EC charge state on probe
Date: Wed, 23 Sep 2026 21:20:16 +0200	[thread overview]
Message-ID: <94bc83bd-5237-4637-acd0-f44df1cdaeb0@weissschuh.net> (raw)
In-Reply-To: <CAFTm+6D7OKYCqfw3yXnRX4jfmbD4ZBcf2TRL-2Tr+6LWSxWP=g@mail.gmail.com>

Hi,

Sep 23, 2026 17:14:31 Matt DeVillier <matt.devillier@gmail.com>:

> Is anything else needed to move this patch forward?

Sebastian picked up the patch, so it will end up in v7.4.
There is nothing else you need to do.

Thomas

> On Sun, Aug 30, 2026 at 9:35 PM Tzung-Bi Shih <tzungbi@kernel.org> wrote:
>>
>> On Fri, Aug 28, 2026 at 09:23:15AM -0500, Matt DeVillier wrote:
>>> The driver previously always forced AUTO with no charge limits at
>>> probe, which discarded sustainer thresholds and modes set by firmware
>>> or firmware setup before the kernel loaded.

(...)

      reply	other threads:[~2026-09-23 19:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24 15:57 [PATCH] " Matt DeVillier
2026-08-25 10:04 ` Tzung-Bi Shih
2026-08-25 10:40 ` Thomas Weißschuh
2026-08-25 12:08 ` [PATCH v2] " Matt DeVillier
2026-08-25 12:09   ` Matt DeVillier
2026-08-25 16:51     ` Thomas Weißschuh
2026-08-26  1:58     ` Tzung-Bi Shih
2026-09-09 21:51     ` Sebastian Reichel
2026-08-28 14:23   ` [PATCH v3] " Matt DeVillier
2026-08-31  2:35     ` Tzung-Bi Shih
2026-09-23 15:14       ` Matt DeVillier
2026-09-23 19:20         ` Thomas Weißschuh [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=94bc83bd-5237-4637-acd0-f44df1cdaeb0@weissschuh.net \
    --to=linux@weissschuh.net \
    --cc=bleung@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=groeck@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=matt.devillier@gmail.com \
    --cc=sre@kernel.org \
    --cc=tzungbi@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
all inboxes | Powered by JetHome®