From: patchwork-bot+linux-arm-msm@kernel.org
To: Rob Clark <robdclark@gmail.com>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v2 0/3] drm/msm: Shrinker fixes and opts
Date: Tue, 29 Dec 2020 20:15:31 +0000 [thread overview]
Message-ID: <160927293184.13751.14272439129941355890.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201116174851.878426-1-robdclark@gmail.com>
Hello:
This series was applied to qcom/linux.git (refs/heads/for-next):
On Mon, 16 Nov 2020 09:48:48 -0800 you wrote:
> From: Rob Clark <robdclark@chromium.org>
>
> The last patch is the main thing, motivated by some cases where we would
> spend a lot of time in msm_gem_shrinker_count(). First two are fixes I
> noticed along the way.
>
> Rob Clark (3):
> drm/msm: Protect obj->active_count under obj lock
> drm/msm/shrinker: We can vmap shrink active_list too
> drm/msm/shrinker: Only iterate dontneed objs
>
> [...]
Here is the summary with links:
- [v2,1/3] drm/msm: Protect obj->active_count under obj lock
https://git.kernel.org/qcom/c/ab5c54cb8835
- [v2,2/3] drm/msm/shrinker: We can vmap shrink active_list too
https://git.kernel.org/qcom/c/fcd371c23c3a
- [v2,3/3] drm/msm/shrinker: Only iterate dontneed objs
https://git.kernel.org/qcom/c/3edfa30f2340
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:[~2020-12-29 20:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 17:48 [PATCH v2 0/3] drm/msm: Shrinker fixes and opts Rob Clark
2020-11-16 17:48 ` [PATCH v2 1/3] drm/msm: Protect obj->active_count under obj lock Rob Clark
2020-11-16 17:48 ` [PATCH v2 2/3] drm/msm/shrinker: We can vmap shrink active_list too Rob Clark
2020-11-16 17:48 ` [PATCH v2 3/3] drm/msm/shrinker: Only iterate dontneed objs Rob Clark
2020-12-29 20:15 ` 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=160927293184.13751.14272439129941355890.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robdclark@gmail.com \
/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