From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: daniel.vetter@intel.com
Cc: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, airlied@linux.ie,
seanpaul@chromium.org, gustavo@padovan.org, jgross@suse.com,
boris.ostrovsky@oracle.com, konrad.wilk@oracle.com,
Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Subject: Re: [PATCH v4 2/2] drm/xen-front: Add support for Xen PV display frontend
Date: Wed, 28 Mar 2018 13:29:46 +0300 [thread overview]
Message-ID: <32481355-27f6-695b-c6c1-8113ea268a33@gmail.com> (raw)
In-Reply-To: <20180328074251.GE14155@phenom.ffwll.local>
[-- Attachment #1: Type: text/plain, Size: 440 bytes --]
Hi, Daniel!
I just noticed I have missed one change in the patch:
the below must be static.
On 03/28/2018 10:42 AM, Daniel Vetter wrote:
> +enum drm_mode_status display_mode_valid(struct drm_crtc *crtc,
> + const struct drm_display_mode *mode)
> +{
> + struct xen_drm_front_drm_pipeline *pipeline =
> + container_of(crtc,
Could you please amend the patch in attachment
when merging, so I don't resend?
Thank you in advance,
Oleksandr
[-- Attachment #2: 0001-drm-xen-front-Make-display_mode_valid-static.patch --]
[-- Type: text/x-patch, Size: 988 bytes --]
>From 3a82d76bd3d954056b760e5d1d09e2f96a2786ef Mon Sep 17 00:00:00 2001
From: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
Date: Wed, 28 Mar 2018 13:24:04 +0300
Subject: [PATCH] drm/xen-front: Make display_mode_valid static
Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com>
---
drivers/gpu/drm/xen/xen_drm_front_kms.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/xen/xen_drm_front_kms.c b/drivers/gpu/drm/xen/xen_drm_front_kms.c
index 545049dfaf0a..bd676be5a0db 100644
--- a/drivers/gpu/drm/xen/xen_drm_front_kms.c
+++ b/drivers/gpu/drm/xen/xen_drm_front_kms.c
@@ -273,7 +273,7 @@ static void display_update(struct drm_simple_display_pipe *pipe,
drm_dev_exit(idx);
}
-enum drm_mode_status display_mode_valid(struct drm_crtc *crtc,
+static enum drm_mode_status display_mode_valid(struct drm_crtc *crtc,
const struct drm_display_mode *mode)
{
struct xen_drm_front_drm_pipeline *pipeline =
--
2.7.4
next prev parent reply other threads:[~2018-03-28 10:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 6:47 [PATCH v4 0/2] " Oleksandr Andrushchenko
2018-03-28 6:47 ` [PATCH v4 1/2] drm: Use srcu to protect drm_device.unplugged Oleksandr Andrushchenko
2018-03-28 7:20 ` [Intel-gfx] " Daniel Vetter
2018-03-28 6:47 ` [PATCH v4 2/2] drm/xen-front: Add support for Xen PV display frontend Oleksandr Andrushchenko
2018-03-28 7:42 ` Daniel Vetter
2018-03-28 7:53 ` Oleksandr Andrushchenko
2018-03-28 10:29 ` Oleksandr Andrushchenko [this message]
2018-03-29 7:17 ` Daniel Vetter
2018-03-29 7:49 ` Oleksandr Andrushchenko
2018-03-29 7:39 ` [RFC PATCH] drm/xen-front: display_mode_valid() can be static kbuild test robot
2018-03-29 7:39 ` [PATCH v4 2/2] drm/xen-front: Add support for Xen PV display frontend kbuild test robot
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=32481355-27f6-695b-c6c1-8113ea268a33@gmail.com \
--to=andr2000@gmail.com \
--cc=airlied@linux.ie \
--cc=boris.ostrovsky@oracle.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@padovan.org \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr_andrushchenko@epam.com \
--cc=seanpaul@chromium.org \
--cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®