From: patchwork-bot+chrome-platform@kernel.org
To: Stephen Boyd <swboyd@chromium.org>
Cc: bleung@chromium.org, linux-kernel@vger.kernel.org,
patches@lists.linux.dev, groeck@chromium.org,
chrome-platform@lists.linux.dev, rajatja@chromium.org,
mka@chromium.org, hsinyi@chromium.org, tzungbi@kernel.org,
evgreen@chromium.org
Subject: Re: [PATCH v3] platform/chrome: cros_ec: Always expose last resume result
Date: Tue, 14 Jun 2022 08:20:13 +0000 [thread overview]
Message-ID: <165519481335.20230.14481630033176207455.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220614075726.2729987-1-swboyd@chromium.org>
Hello:
This patch was applied to chrome-platform/linux.git (for-kernelci)
by Tzung-Bi Shih <tzungbi@kernel.org>:
On Tue, 14 Jun 2022 00:57:26 -0700 you wrote:
> The last resume result exposing logic in cros_ec_sleep_event()
> incorrectly requires S0ix support, which doesn't work on ARM based
> systems where S0ix doesn't exist. That's because cros_ec_sleep_event()
> only reports the last resume result when the EC indicates the last sleep
> event was an S0ix resume. On ARM systems, the last sleep event is always
> S3 resume, but the EC can still detect sleep hang events in case some
> other part of the AP is blocking sleep.
>
> [...]
Here is the summary with links:
- [v3] platform/chrome: cros_ec: Always expose last resume result
https://git.kernel.org/chrome-platform/c/74bb746407bf
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:[~2022-06-14 8:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 7:57 [PATCH v3] platform/chrome: cros_ec: Always expose last resume result Stephen Boyd
2022-06-14 8:20 ` patchwork-bot+chrome-platform [this message]
2022-06-16 8:10 ` 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=165519481335.20230.14481630033176207455.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=evgreen@chromium.org \
--cc=groeck@chromium.org \
--cc=hsinyi@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=patches@lists.linux.dev \
--cc=rajatja@chromium.org \
--cc=swboyd@chromium.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;
as well as URLs for NNTP newsgroup(s).