From: patchwork-bot+chrome-platform@kernel.org
To: Tim Van Patten <timvp@chromium.org>
Cc: linux-kernel@vger.kernel.org, robbarnes@google.com,
lalithkraj@google.com, rrangel@chromium.org, bleung@chromium.org,
groeck@chromium.org, chrome-platform@lists.linux.dev
Subject: Re: [PATCH] [v9] platform/chrome: cros_ec_lpc: Move host command to prepare/complete
Date: Mon, 22 May 2023 08:10:20 +0000 [thread overview]
Message-ID: <168474302006.27846.3771837102628763642.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230515142552.1.I17cae37888be3a8683911991602f18e482e7a621@changeid>
Hello:
This patch was applied to chrome-platform/linux.git (for-next)
by Tzung-Bi Shih <tzungbi@kernel.org>:
On Mon, 15 May 2023 14:25:52 -0600 you wrote:
> Update cros_ec_lpc_pm_ops to call cros_ec_lpc_prepare() during PM
> .prepare() and cros_ec_lpc_complete() during .complete(). This moves the
> host command that the AP sends and allows the EC to log entry/exit of
> AP's suspend/resume more accurately.
>
> Changes in v9:
> - Remove log statements.
> - Ignore return value from cros_ec_resume().
>
> [...]
Here is the summary with links:
- [v9] platform/chrome: cros_ec_lpc: Move host command to prepare/complete
https://git.kernel.org/chrome-platform/c/4b9abbc132b8
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-05-22 8:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 20:25 [PATCH] [v9] platform/chrome: cros_ec_lpc: Move host command to prepare/complete Tim Van Patten
2023-05-17 2:35 ` Tzung-Bi Shih
2023-05-17 15:56 ` Tim Van Patten
2023-05-18 1:38 ` Tzung-Bi Shih
2023-05-18 16:47 ` Tim Van Patten
2023-05-19 1:55 ` Tzung-Bi Shih
2023-05-19 15:32 ` Tim Van Patten
2023-05-22 2:00 ` patchwork-bot+chrome-platform
2023-05-22 8: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=168474302006.27846.3771837102628763642.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=bleung@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=lalithkraj@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robbarnes@google.com \
--cc=rrangel@chromium.org \
--cc=timvp@chromium.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