From: patchwork-bot+chrome-platform@kernel.org
To: Karthikeyan Ramasubramanian <kramasub@chromium.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
lalithkraj@chromium.org, chrome-platform@lists.linux.dev,
bleung@chromium.org, groeck@chromium.org, tzungbi@kernel.org
Subject: Re: [PATCH v2] chrome/cros_ec: Handle events during suspend after resume completion
Date: Tue, 30 Apr 2024 01:40:30 +0000 [thread overview]
Message-ID: <171444123043.8598.17705280071551125756.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240429121343.v2.1.If2e0cef959f1f6df9f4d1ab53a97c54aa54208af@changeid>
Hello:
This patch was applied to chrome-platform/linux.git (for-next)
by Tzung-Bi Shih <tzungbi@kernel.org>:
On Mon, 29 Apr 2024 12:13:45 -0600 you wrote:
> Commit 47ea0ddb1f56 ("platform/chrome: cros_ec_lpc: Separate host
> command and irq disable") re-ordered the resume sequence. Before that
> change, cros_ec resume sequence is:
> 1) Enable IRQ
> 2) Send resume event
> 3) Handle events during suspend
>
> [...]
Here is the summary with links:
- [v2] chrome/cros_ec: Handle events during suspend after resume completion
https://git.kernel.org/chrome-platform/c/2fbe479c0024
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:[~2024-04-30 1:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 18:13 [PATCH v2] chrome/cros_ec: Handle events during suspend after resume completion Karthikeyan Ramasubramanian
2024-04-30 1:40 ` patchwork-bot+chrome-platform [this message]
2024-04-30 1:40 ` 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=171444123043.8598.17705280071551125756.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=kramasub@chromium.org \
--cc=lalithkraj@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).