From: Mark yao <mark.yao@rock-chips.com>
To: Dave Airlie <airlied@gmail.com>
Cc: "open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [GIT PULL] drm/rockchip: some fixes
Date: Sat, 17 Sep 2016 13:41:26 +0800 [thread overview]
Message-ID: <57DCD786.6000102@rock-chips.com> (raw)
In-Reply-To: <CAPM=9tyGT_5_QpqWpU+=E7GfrGZz0rWHn76WDMJoV9VFwedBcQ@mail.gmail.com>
On 2016年09月13日 08:20, Dave Airlie wrote:
> On 10 September 2016 at 12:57, Mark yao <mark.yao@rock-chips.com> wrote:
>> Hi Dave
>> Here are some little fixes for rockchip drm, looks good for me, and
>> there is no doubt on them, So I'd like you can land them.
>>
>> Thanks.
>>
>> The following changes since commit 603f2c9f45c6620afd65b60ec084c1ea7c36b2ec:
>>
>> Merge tag 'drm-vc4-fixes-2016-08-29' of https://github.com/anholt/linux
>> into drm-fixes (2016-09-02 15:55:15 +1000)
>>
>> are available in the git repository at:
>>
>>
>> https://github.com/markyzq/kernel-drm-rockchip.git
> Something is wrong with this pull request, there is no branch name.
>
> Please test pull requests are complete before sending,
>
> Thanks,
> Dave.
>
>
>
Hi Dave
Sorry, here is correct one.
The following changes since commit 603f2c9f45c6620afd65b60ec084c1ea7c36b2ec:
Merge tag 'drm-vc4-fixes-2016-08-29' of
https://github.com/anholt/linux into drm-fixes (2016-09-02 15:55:15 +1000)
are available in the git repository at:
https://github.com/markyzq/kernel-drm-rockchip.git
drm-rockchip-fixes-2016-09-10
for you to fetch changes up to d59cacfb69ee46878373284403595e30f718218a:
drm/rockchip: mark symbols static where possible (2016-09-10 10:48:37
+0800)
----------------------------------------------------------------
Baoyou Xie (2):
drm/rockchip: add missing header dependencies
drm/rockchip: mark symbols static where possible
Chris Zhong (1):
drm/rockchip: vop: make vop register setting take effect
Douglas Anderson (1):
drm/rockchip: Properly adjust to a true clock in adjusted_mode
Mark Yao (1):
drm/rockchip: fix fbdev crash when not use DRM_FBDEV_EMULATION
drivers/gpu/drm/rockchip/rockchip_drm_drv.c | 10 +++++-----
drivers/gpu/drm/rockchip/rockchip_drm_drv.h | 2 +-
drivers/gpu/drm/rockchip/rockchip_drm_fb.c | 2 +-
drivers/gpu/drm/rockchip/rockchip_drm_fbdev.c | 18 +++++++++++-------
drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 7 ++++++-
5 files changed, 24 insertions(+), 15 deletions(-)
--
Mark Yao
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-09-17 5:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-10 2:57 [GIT PULL] drm/rockchip: some fixes Mark yao
2016-09-13 0:20 ` Dave Airlie
2016-09-17 5:41 ` Mark yao [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-22 0:54 Mark yao
2017-02-22 16:09 ` Sean Paul
2017-02-23 2:03 ` Mark yao
2017-02-23 18:01 ` Sean Paul
2017-02-24 0:42 ` Mark yao
2016-07-19 2:32 Mark yao
2016-05-03 6:21 Mark yao
2016-03-28 6:54 [GIT PULL]: " Mark yao
2015-07-13 6:22 [GIT PULL] " Mark yao
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=57DCD786.6000102@rock-chips.com \
--to=mark.yao@rock-chips.com \
--cc=airlied@gmail.com \
--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 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.