From: patchwork-bot+linux-arm-msm@kernel.org
To: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 0/2] drm/msm/a6xx: LLCC related fix and cleanup
Date: Mon, 01 Mar 2021 19:59:42 +0000 [thread overview]
Message-ID: <161462878267.6187.10770105143273200562.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1610366113.git.saiprakash.ranjan@codeaurora.org>
Hello:
This series was applied to qcom/linux.git (refs/heads/for-next):
On Mon, 11 Jan 2021 17:34:07 +0530 you wrote:
> Patch 1 is a fix to not set the attributes when CONFIG_QCOM_LLCC
> is disabled and Patch 2 is a cleanup to create an a6xx specific address
> space.
>
> Sai Prakash Ranjan (2):
> drm/msm: Add proper checks for GPU LLCC support
> drm/msm/a6xx: Create an A6XX GPU specific address space
>
> [...]
Here is the summary with links:
- [1/2] drm/msm: Add proper checks for GPU LLCC support
https://git.kernel.org/qcom/c/276619c0923f
- [2/2] drm/msm/a6xx: Create an A6XX GPU specific address space
https://git.kernel.org/qcom/c/45596f254061
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:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 12:04 [PATCH 0/2] drm/msm/a6xx: LLCC related fix and cleanup Sai Prakash Ranjan
2021-01-11 12:04 ` [PATCH 1/2] drm/msm: Add proper checks for GPU LLCC support Sai Prakash Ranjan
2021-01-11 12:04 ` [PATCH 2/2] drm/msm/a6xx: Create an A6XX GPU specific address space Sai Prakash Ranjan
2021-01-20 11:04 ` AngeloGioacchino Del Regno
2021-01-20 16:27 ` Rob Clark
2021-01-21 6:25 ` Sai Prakash Ranjan
2021-01-20 16:18 ` [Freedreno] " Rob Clark
2021-01-21 6:06 ` Sai Prakash Ranjan
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=161462878267.6187.10770105143273200562.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=saiprakash.ranjan@codeaurora.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.