From: patchwork-bot+chrome-platform@kernel.org
To: Rob Barnes <robbarnes@google.com>
Cc: chrome-platform@lists.linux.dev, dnojiri@chromium.org,
tzungbi@kernel.org, pmalani@chromium.org
Subject: Re: [PATCH v4] platform/chrome: cros_ec: Report EC panic as uevent
Date: Mon, 15 May 2023 05:20:18 +0000 [thread overview]
Message-ID: <168412801871.16595.14801750952836079496.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230509232624.3120347-1-robbarnes@google.com>
Hello:
This patch was applied to chrome-platform/linux.git (for-kernelci)
by Tzung-Bi Shih <tzungbi@kernel.org>:
On Tue, 9 May 2023 23:26:24 +0000 you wrote:
> Create a uevent when an EC panic is detected. This will allow udev rules
> to trigger when a panic occurs. For example, a udev rule could be added to
> capture an EC coredump. This approach avoids the need to stuff all the
> processing into the driver.
>
> Signed-off-by: Rob Barnes <robbarnes@google.com>
> Reviewed-by: Prashant Malani <pmalani@chromium.org>
>
> [...]
Here is the summary with links:
- [v4] platform/chrome: cros_ec: Report EC panic as uevent
https://git.kernel.org/chrome-platform/c/2cbf475a04b2
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-05-15 5:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 17:46 [PATCH] platform/chrome: cros_ec: Report EC panic as uevent Rob Barnes
2023-04-20 21:08 ` Prashant Malani
2023-04-24 16:44 ` Rob Barnes
2023-05-09 22:22 ` [PATCH v2] " Rob Barnes
2023-05-09 22:59 ` Prashant Malani
2023-05-09 23:19 ` [PATCH v3] " Rob Barnes
2023-05-09 23:25 ` Prashant Malani
2023-05-09 23:26 ` [PATCH v4] " Rob Barnes
2023-05-15 5:20 ` patchwork-bot+chrome-platform [this message]
2023-05-19 2:00 ` 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=168412801871.16595.14801750952836079496.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=chrome-platform@lists.linux.dev \
--cc=dnojiri@chromium.org \
--cc=pmalani@chromium.org \
--cc=robbarnes@google.com \
--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