From: patchwork-bot+chrome-platform@kernel.org
To: Rob Barnes <robbarnes@google.com>
Cc: groeck@chromium.org, pmalani@chromium.org,
chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org,
dtor@chromium.org
Subject: Re: [PATCH v3 0/2] Handle CrOS EC Panics
Date: Fri, 06 Jan 2023 03:50:16 +0000 [thread overview]
Message-ID: <167297701631.12088.14549595747542948276.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230104011524.369764-1-robbarnes@google.com>
Hello:
This series was applied to chrome-platform/linux.git (for-kernelci)
by Tzung-Bi Shih <tzungbi@kernel.org>:
On Wed, 4 Jan 2023 01:15:22 +0000 you wrote:
> Currently the OS ignores EC panics when they occur.
> After reporting a panic, the EC will force a hard reset,
> possibly after a short delay. This may cause loss of data.
>
> These patches add a handler for CrOS EC panics. When
> a panic is detected the OS will attempt to flush critical
> data for debugging purposes and attempt an orderly shutdown.
>
> [...]
Here is the summary with links:
- [v3,1/2] platform/chrome: cros_ec: Poll EC log on EC panic
https://git.kernel.org/chrome-platform/c/d90fa2c64d59
- [v3,2/2] platform/chrome: cros_ec: Shutdown on EC Panic
https://git.kernel.org/chrome-platform/c/957445d730ba
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-01-06 3:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 1:15 [PATCH v3 0/2] Handle CrOS EC Panics Rob Barnes
2023-01-04 1:15 ` [PATCH v3 1/2] platform/chrome: cros_ec: Poll EC log on EC panic Rob Barnes
2023-01-05 4:40 ` Prashant Malani
2023-01-10 22:09 ` Marek Szyprowski
2023-01-04 1:15 ` [PATCH v3 2/2] platform/chrome: cros_ec: Shutdown on EC Panic Rob Barnes
2023-01-04 18:41 ` Prashant Malani
2023-01-06 3:50 ` patchwork-bot+chrome-platform [this message]
2023-01-09 5:30 ` [PATCH v3 0/2] Handle CrOS EC Panics patchwork-bot+chrome-platform
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=167297701631.12088.14549595747542948276.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=chrome-platform@lists.linux.dev \
--cc=dtor@chromium.org \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmalani@chromium.org \
--cc=robbarnes@google.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