Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH v3] platform/chrome: cros_ec: Always expose last resume result
From:   patchwork-bot+chrome-platform@kernel.org
Message-Id: <165519481335.20230.14481630033176207455.git-patchwork-notify@kernel.org>
Date:   Tue, 14 Jun 2022 08:20:13 +0000
References: <20220614075726.2729987-1-swboyd@chromium.org>
In-Reply-To: <20220614075726.2729987-1-swboyd@chromium.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
Precedence: bulk

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