The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Benson Leung <bleung@chromium.org>,
	Tzung-Bi Shih <tzungbi@kernel.org>,
	Andrei Kuchynski <akuchynski@chromium.org>
Cc: Guenter Roeck <groeck@chromium.org>,
	Gwendal Grignou <gwendal@chromium.org>,
	chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] mfd: platform/chrome: Catch EC feature read errors during probe
Date: Thu, 23 Jul 2026 17:05:53 +0100	[thread overview]
Message-ID: <20260723160553.GC3526803@google.com> (raw)
In-Reply-To: <178482259319.3530477.8287706988972276877.b4-ty@b4>

On Thu, 23 Jul 2026, Lee Jones wrote:

> On Mon, 08 Jun 2026 21:15:16 +0000, Andrei Kuchynski wrote:
> > This series fixes a sysfs duplicate name collision that occurs when the
> > Fingerprint device fails to respond during probe, causing it to
> > incorrectly fall back to the generic 'cros_ec' name.
> > 
> > Changes in v2:
> > - Split into a 2-patch series.
> > - Carried over Acked-by from Tzung-Bi Shih for Patch 1.
> > - Fixed an ec->class_dev resource leak by utilizing 'goto failed;'.
> > - Moved class_dev initialization to prevent a missing release()
> >   callback warning on the error path.
> > 
> > [...]
> 
> Applied, thanks!
> 
> [1/2] platform/chrome: cros_ec_proto: Introduce cros_ec_read_features helper
>       commit: d6ae9f9b9bd373461442f17ef157ed9ee850a413
> [2/2] mfd: cros_ec: Read EC features during probe to catch transfer error
>       commit: 5855464dff6a2171847463775c7cdac92742e0f9

Build testing now.

Note to self: ib-mfd-platform-chrome-7.3

-- 
Lee Jones

      reply	other threads:[~2026-07-23 16:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-08 21:15 [PATCH v2 0/2] mfd: platform/chrome: Catch EC feature read errors during probe Andrei Kuchynski
2026-06-08 21:15 ` [PATCH v2 1/2] platform/chrome: cros_ec_proto: Introduce cros_ec_read_features helper Andrei Kuchynski
2026-06-08 21:15 ` [PATCH v2 2/2] mfd: cros_ec: Read EC features during probe to catch transfer error Andrei Kuchynski
2026-06-18  8:40   ` Lee Jones
2026-06-18  9:31     ` Tzung-Bi Shih
2026-06-18 11:21       ` Lee Jones
2026-07-17  6:40         ` Tzung-Bi Shih
2026-07-23 16:03 ` [PATCH v2 0/2] mfd: platform/chrome: Catch EC feature read errors during probe Lee Jones
2026-07-23 16:05   ` Lee Jones [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=20260723160553.GC3526803@google.com \
    --to=lee@kernel.org \
    --cc=akuchynski@chromium.org \
    --cc=bleung@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=groeck@chromium.org \
    --cc=gwendal@chromium.org \
    --cc=linux-kernel@vger.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