From: patchwork-bot+linux-arm-msm@kernel.org
To: Eric Anholt <eric@anholt.net>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v3 0/3] drm/msm: fix for "Timeout waiting for GMU OOB set GPU_SET: 0x0"
Date: Mon, 01 Mar 2021 19:59:43 +0000 [thread overview]
Message-ID: <161462878373.6187.1748332752540063152.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210128210332.1690609-1-eric@anholt.net>
Hello:
This series was applied to qcom/linux.git (refs/heads/for-next):
On Thu, 28 Jan 2021 13:03:29 -0800 you wrote:
> Updated commit messages over v2, no code changes.
>
> Eric Anholt (3):
> drm/msm: Fix race of GPU init vs timestamp power management.
> drm/msm: Fix races managing the OOB state for timestamp vs timestamps.
> drm/msm: Clean up GMU OOB set/clear handling.
>
> [...]
Here is the summary with links:
- [v3,1/3] drm/msm: Fix race of GPU init vs timestamp power management.
https://git.kernel.org/qcom/c/7a7cbf2a8197
- [v3,2/3] drm/msm: Fix races managing the OOB state for timestamp vs timestamps.
https://git.kernel.org/qcom/c/5f98b33b04c0
- [v3,3/3] drm/msm: Clean up GMU OOB set/clear handling.
https://git.kernel.org/qcom/c/555c50a4a19b
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:[~2021-03-01 20:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 21:03 [PATCH v3 0/3] drm/msm: fix for "Timeout waiting for GMU OOB set GPU_SET: 0x0" Eric Anholt
2021-01-28 21:03 ` Eric Anholt
2021-01-28 21:03 ` [PATCH v3 1/3] drm/msm: Fix race of GPU init vs timestamp power management Eric Anholt
2021-01-28 21:03 ` Eric Anholt
2021-01-28 21:03 ` [PATCH v3 2/3] drm/msm: Fix races managing the OOB state for timestamp vs timestamps Eric Anholt
2021-01-28 21:03 ` Eric Anholt
2021-01-28 21:03 ` [PATCH v3 3/3] drm/msm: Clean up GMU OOB set/clear handling Eric Anholt
2021-01-28 21:03 ` Eric Anholt
2021-03-01 19:59 ` patchwork-bot+linux-arm-msm [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=161462878373.6187.1748332752540063152.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=eric@anholt.net \
--cc=linux-arm-msm@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.