From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Hongyan Xu <getshell@seu.edu.cn>
Cc: bleung@chromium.org, groeck@chromium.org,
chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org,
jianhao.xu@seu.edu.cn
Subject: Re: [PATCH v2 1/2] platform/chrome: cros_ec_debugfs: clean up console log on probe failure
Date: Thu, 30 Jul 2026 01:48:33 +0000 [thread overview]
Message-ID: <amqtcf3VEoi0tIzw@google.com> (raw)
In-Reply-To: <c00974953a1b952f51f0f021d7f9fad134159909.1785320940.git.getshell@seu.edu.cn>
On Wed, Jul 29, 2026 at 06:32:16PM +0800, Hongyan Xu wrote:
> cros_ec_create_console_log() starts log_poll_work when console logging is
> supported. If the following panic notifier registration fails, probe
> removes the debugfs entries but leaves the delayed work scheduled. The
> work can then access devm-managed data after the failed probe tears it
> down.
>
> Add a dedicated error label for failures after successful console log
> setup. Earlier failures keep using the existing debugfs-only cleanup
> path.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git for-next
[1/2] platform/chrome: cros_ec_debugfs: clean up console log on probe failure
commit: 5d187600c4603b8f7812b12ce359a11ad7a7fd3a
[2/2] platform/chrome: cros_ec_debugfs: unregister panic notifier
commit: e5954d3031fb55dd31aa59bae477d63c68e941c0
Thanks!
prev parent reply other threads:[~2026-07-30 1:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 10:32 [PATCH v2 1/2] platform/chrome: cros_ec_debugfs: clean up console log on probe failure Hongyan Xu
2026-07-29 10:32 ` [PATCH v2 2/2] platform/chrome: cros_ec_debugfs: unregister panic notifier Hongyan Xu
2026-07-30 1:48 ` Tzung-Bi Shih [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=amqtcf3VEoi0tIzw@google.com \
--to=tzungbi@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=getshell@seu.edu.cn \
--cc=groeck@chromium.org \
--cc=jianhao.xu@seu.edu.cn \
--cc=linux-kernel@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