Linux-Rockchip Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark yao <mark.yao@rock-chips.com>
To: David Airlie <airlied@linux.ie>,
	dri-devel <dri-devel@lists.freedesktop.org>
Cc: "open list:ARM/Rockchip SoC..." <linux-rockchip@lists.infradead.org>
Subject: [GIT PULL] drm/rockchip: fixes and be rockchip/drm maintainer
Date: Mon, 20 Apr 2015 09:30:06 +0800	[thread overview]
Message-ID: <5534569E.2090601@rock-chips.com> (raw)

Hi Dave
     I'm interesting to maintain the rockchip drm, so add entry for 
Rockchip drm.
     and some fixes.

     Can you land them?

The following changes since commit aa219a0dd7774e2454a5687e7d38e947a131cdee:

   Merge tag 'drm-intel-next-fixes-2015-04-15' of 
git://anongit.freedesktop.org/drm-intel into drm-next (2015-04-16 
08:34:51 +1000)

are available in the git repository at:


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

for you to fetch changes up to 3ea68922fc4148abc97557df43d4ba9a136b1c8d:

   drm/rockchip: fix error check when getting irq (2015-04-20 09:02:31 
+0800)

----------------------------------------------------------------
Heiko Stuebner (2):
       MAINTAINERS: add entry for Rockchip drm drivers
       drm/rockchip: fix error check when getting irq

  MAINTAINERS                                 |    7 +++++++
  drivers/gpu/drm/rockchip/rockchip_drm_vop.c |    9 +++++----
  2 files changed, 12 insertions(+), 4 deletions(-)

-- 
Mark

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

             reply	other threads:[~2015-04-20  1:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20  1:30 Mark yao [this message]
2015-04-30  7:32 ` [GIT PULL] drm/rockchip: fixes and be rockchip/drm maintainer Heiko Stübner

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=5534569E.2090601@rock-chips.com \
    --to=mark.yao@rock-chips.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-rockchip@lists.infradead.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