From: patchwork-bot+linux-arm-msm@kernel.org
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 0/2] drm: Build fixes for msm and mediatek
Date: Tue, 29 Dec 2020 20:15:32 +0000 [thread overview]
Message-ID: <160927293249.13751.7545901236405411045.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201109103242.19544-1-tzimmermann@suse.de>
Hello:
This series was applied to qcom/linux.git (refs/heads/for-next):
On Mon, 9 Nov 2020 11:32:40 +0100 you wrote:
> Commit 49a3f51dfeee ("drm/gem: Use struct dma_buf_map in GEM vmap ops and
> convert GEM backends") changed DRM's internal GEM vmap callbacks. Msm and
> mediatek were forgotten during the conversion.
>
> Thomas Zimmermann (2):
> drm/msm: Use struct dma_buf_map in GEM vmap ops
> drm/mediatek: Use struct dma_buf_map in GEM vmap ops
>
> [...]
Here is the summary with links:
- [1/2] drm/msm: Use struct dma_buf_map in GEM vmap ops
https://git.kernel.org/qcom/c/b47f9f92d6fe
- [2/2] drm/mediatek: Use struct dma_buf_map in GEM vmap ops
https://git.kernel.org/qcom/c/7e542ff8b463
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: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 10:32 [PATCH 0/2] drm: Build fixes for msm and mediatek Thomas Zimmermann
2020-11-09 10:32 ` Thomas Zimmermann
2020-11-09 10:32 ` [PATCH 1/2] drm/msm: Use struct dma_buf_map in GEM vmap ops Thomas Zimmermann
2020-11-09 10:32 ` Thomas Zimmermann
2020-11-09 10:32 ` Thomas Zimmermann
2020-11-09 10:32 ` Thomas Zimmermann
2020-11-09 10:32 ` Thomas Zimmermann
2020-11-09 10:32 ` Thomas Zimmermann
2020-11-13 8:59 ` kernel test robot
2020-11-16 6:17 ` kernel test robot
2020-11-09 10:32 ` [PATCH 2/2] drm/mediatek: " Thomas Zimmermann
2020-11-09 10:32 ` Thomas Zimmermann
2020-11-09 10:32 ` Thomas Zimmermann
2020-11-09 10:32 ` Thomas Zimmermann
2020-11-09 10:32 ` Thomas Zimmermann
2020-11-09 10:32 ` Thomas Zimmermann
2020-11-11 14:23 ` Chun-Kuang Hu
2020-11-11 14:23 ` Chun-Kuang Hu
2020-11-11 14:23 ` Chun-Kuang Hu
2020-11-11 14:23 ` Chun-Kuang Hu
2020-11-11 14:23 ` Chun-Kuang Hu
2020-11-13 9:30 ` kernel test robot
2020-11-14 7:30 ` kernel test robot
2020-11-16 6:41 ` kernel test robot
2020-11-10 9:33 ` [PATCH 0/2] drm: Build fixes for msm and mediatek Daniel Vetter
2020-11-10 9:33 ` Daniel Vetter
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=160927293249.13751.7545901236405411045.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=tzimmermann@suse.de \
/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.