From: patchwork-bot+chrome-platform@kernel.org
To: Rob Barnes <robbarnes@google.com>
Cc: pmalani@chromium.org, chrome-platform@lists.linux.dev,
briannorris@chromium.org, bleung@chromium.org,
groeck@chromium.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers/cros_ec: Emergency sync filesystem on EC panic
Date: Wed, 19 Jul 2023 02:10:22 +0000 [thread overview]
Message-ID: <168973262262.24960.14264135195868218640.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230717232932.1.I361812b405bd07772f66660624188339ab158772@changeid>
Hello:
This patch was applied to chrome-platform/linux.git (for-next)
by Tzung-Bi Shih <tzungbi@kernel.org>:
On Mon, 17 Jul 2023 23:29:32 +0000 you wrote:
> Perform an emergency filesystem sync when an EC panic is reported. An
> emergency sync actually performs two syncs internally in case some
> inodes or pages are temporarily locked.
>
> hw_protection_shutdown is replaced for a few reasons. It is unnecessary
> because the EC will force reset either way. hw_protection_shutdown does
> not reliably sync filesystem before shutting down. emergency_sync is not
> synchronous so hw_protection_shutdown may interrupt emergency_sync.
>
> [...]
Here is the summary with links:
- drivers/cros_ec: Emergency sync filesystem on EC panic
https://git.kernel.org/chrome-platform/c/a6edd5f5d9cc
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-07-19 2:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 23:29 [PATCH] drivers/cros_ec: Emergency sync filesystem on EC panic Rob Barnes
2023-07-17 23:48 ` Benson Leung
2023-07-17 23:54 ` Guenter Roeck
2023-07-18 2:50 ` patchwork-bot+chrome-platform
2023-07-19 2:10 ` patchwork-bot+chrome-platform [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=168973262262.24960.14264135195868218640.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=bleung@chromium.org \
--cc=briannorris@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--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