From: patchwork-bot+linux-arm-msm@kernel.org
To: Robin Murphy <robin.murphy@arm.com>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] drm/msm: Add missing stub definition
Date: Tue, 29 Dec 2020 20:15:36 +0000 [thread overview]
Message-ID: <160927293604.13751.18370874320845912852.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <b9117317819c8b63d558231e6b88410ea717065e.1603716447.git.robin.murphy@arm.com>
Hello:
This patch was applied to qcom/linux.git (refs/heads/for-next):
On Mon, 26 Oct 2020 12:48:37 +0000 you wrote:
> DRM_MSM fails to build with DRM_MSM_DP=n; add the missing stub.
>
> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> ---
> drivers/gpu/drm/msm/msm_drv.h | 5 +++++
> 1 file changed, 5 insertions(+)
Here is the summary with links:
- drm/msm: Add missing stub definition
https://git.kernel.org/qcom/c/a0b21e0ad294
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:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 12:48 [PATCH] drm/msm: Add missing stub definition Robin Murphy
2020-10-26 15:28 ` 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=160927293604.13751.18370874320845912852.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robin.murphy@arm.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;
as well as URLs for NNTP newsgroup(s).