dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: zhaojunwang <zhaojunwang@pku.edu.cn>
To: "John Hunter" <zhjwpku@gmail.com>,
	dri-devel <dri-devel@lists.freedesktop.org>
Cc: "Daniel Vetter" <daniel.vetter@ffwll.ch>,
	"Matthew Garrett" <mjg59@coreos.com>,
	"Dave Airlie" <airlied@redhat.com>
Subject: Re: [PATCH 7/7] drm/cirrus: add DRIVER_ATOMIC to .driver_features
Date: Wed, 5 Aug 2015 15:14:03 +0800	[thread overview]
Message-ID: <tencent_23FEDBE063C28C547B6872AD@qq.com> (raw)
In-Reply-To: <1438758531-4384-1-git-send-email-zhjwpku@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1618 bytes --]

Can you pls review these patch series, thanks a lot for your time.




------------------ Original ------------------
From:  "John Hunter";<zhjwpku@gmail.com>;
Date:  Wed, Aug 5, 2015 03:08 PM
To:  "dri-devel"<dri-devel@lists.freedesktop.org>; 
Cc:  "Zhao Junwang"<zhjwpku@gmail.com>; "Daniel Vetter"<daniel.vetter@ffwll.ch>; "Gerd Hoffmann"<kraxel@redhat.com>; "Matthew Garrett"<mjg59@coreos.com>; "Dave Airlie"<airlied@redhat.com>; "Zhao Junwang"<zhaojunwang@pku.edu.cn>; 
Subject:  [PATCH 7/7] drm/cirrus: add DRIVER_ATOMIC to .driver_features



From: Zhao Junwang <zhjwpku@gmail.com>

Since  driver is now fully atomic, we should add DRIVER_ATOMIC to
.driver_features

Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Gerd Hoffmann <kraxel@redhat.com>
Cc: Matthew Garrett <mjg59@coreos.com>
Cc: Dave Airlie <airlied@redhat.com>
Cc: Zhao Junwang <zhaojunwang@pku.edu.cn>
Signed-off-by: Zhao Junwang <zhjwpku@gmail.com>
---
 drivers/gpu/drm/cirrus/cirrus_drv.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/cirrus/cirrus_drv.c b/drivers/gpu/drm/cirrus/cirrus_drv.c
index 80f1cd2..742647b 100644
--- a/drivers/gpu/drm/cirrus/cirrus_drv.c
+++ b/drivers/gpu/drm/cirrus/cirrus_drv.c
@@ -130,7 +130,7 @@ static const struct file_operations cirrus_driver_fops = {
 #endif
 };
 static struct drm_driver driver = {
-	.driver_features = DRIVER_MODESET | DRIVER_GEM,
+	.driver_features = DRIVER_MODESET | DRIVER_GEM | DRIVER_ATOMIC,
 	.load = cirrus_driver_load,
 	.unload = cirrus_driver_unload,
 	.set_busid = drm_pci_set_busid,
-- 
1.7.10.4

[-- Attachment #1.2: Type: text/html, Size: 2157 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-08-05  7:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05  7:08 [PATCH 7/7] drm/cirrus: add DRIVER_ATOMIC to .driver_features John Hunter
2015-08-05  7:14 ` zhaojunwang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-08-05  7:22 [PATCH 0/7] drm/cirrus: convert cirrus to atomic mode-setting John Hunter
2015-08-05  7:22 ` [PATCH 7/7] drm/cirrus: add DRIVER_ATOMIC to .driver_features John Hunter
2015-07-30 10:08 [PATCH 0/7] drm/cirrus: convert cirrus to atomic mode-setting John Hunter
2015-07-30 10:08 ` [PATCH 7/7] drm/cirrus: add DRIVER_ATOMIC to .driver_features John Hunter

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=tencent_23FEDBE063C28C547B6872AD@qq.com \
    --to=zhaojunwang@pku.edu.cn \
    --cc=airlied@redhat.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=mjg59@coreos.com \
    --cc=zhjwpku@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