All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark yao <mark.yao@rock-chips.com>
To: Daniel Kurtz <djkurtz@chromium.org>, David Airlie <airlied@linux.ie>
Cc: DRM DRIVERS <dri-devel@lists.freedesktop.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] drm/rockchip: Only alloc a kmap for fbdev gem object
Date: Thu, 22 Jan 2015 11:52:49 +0800	[thread overview]
Message-ID: <54C07411.2070905@rock-chips.com> (raw)
In-Reply-To: <1421045914-26948-1-git-send-email-djkurtz@chromium.org>

Hi Dave
     I'd like this patch, some gem object need not be mapped into kernel 
address space.

The following changes since commit 281d1bbd34b734e4f22b30b6f3b673dda46a7470:

   Merge remote-tracking branch 'origin/master' into drm-next 
(2015-01-22 10:44:41 +1000)

are available in the git repository at:


   https://github.com/markyzq/kernel-drm-rockchip.git drm_next

for you to fetch changes up to 5727d1ac71026dd5dd1454b8cc51d409f05f1808:

   drm/rockchip: Only alloc a kmap for fbdev gem object (2015-01-22 
11:19:13 +0800)

----------------------------------------------------------------
Daniel Kurtz (1):
       drm/rockchip: Only alloc a kmap for fbdev gem object

  drivers/gpu/drm/rockchip/rockchip_drm_fbdev.c |    2 +-
  drivers/gpu/drm/rockchip/rockchip_drm_gem.c   |   17 ++++++++++++-----
  drivers/gpu/drm/rockchip/rockchip_drm_gem.h   |    3 ++-
  3 files changed, 15 insertions(+), 7 deletions(-)

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

      reply	other threads:[~2015-01-22  3:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-12  6:58 [PATCH] drm/rockchip: Only alloc a kmap for fbdev gem object Daniel Kurtz
2015-01-12  6:58 ` Daniel Kurtz
2015-01-22  3:52 ` Mark yao [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=54C07411.2070905@rock-chips.com \
    --to=mark.yao@rock-chips.com \
    --cc=airlied@linux.ie \
    --cc=djkurtz@chromium.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.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.