From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] drm/rockchip: fixes
Date: Sat, 21 Nov 2015 22:50:10 +0100 [thread overview]
Message-ID: <3016892.vBtLqFySEY@phil> (raw)
In-Reply-To: <56429253.6050107@rock-chips.com>
Hi Mark,
Am Mittwoch, 11. November 2015, 08:56:51 schrieb Mark yao:
> Here are some fixes for drm/rockchip:
> drm/rockchip can't work now, we need the patch
> Revert "drm/rockchip: Convert the probe function to the
> generic drm_of_component_probe()"
> and other three fixes are also needed.
>
> I'd like you can land them.
>
> The following changes since commit
> 816d2206f0f9953ca854e4ff1a2749a5cbd62715:
>
> Merge tag 'drm-intel-next-fixes-2015-11-06' of
> git://anongit.freedesktop.org/drm-intel into drm-next (2015-11-07
> 17:16:59 +1000)
>
> are available in the git repository at:
>
>
> https://github.com/markyzq/kernel-drm-rockchip.git drm-rockchip-2015-11-11
>
> for you to fetch changes up to 55ac58b5d27a35b8caaa9bd07eb1d2899473130c:
>
> drm/rockchip: vop: fix window origin calculation (2015-11-11 08:36:18
> +0800)
>
> ----------------------------------------------------------------
> Dominik Behr (1):
> drm/rockchip: vop: fix window origin calculation
>
> Heiko Stuebner (1):
> drm/rockchip: unset pgoff when mmap'ing gems
>
> Mark Yao (1):
> Revert "drm/rockchip: Convert the probe function to the generic
> drm_of_component_probe()"
Dave already applied this patch by himself, back before -rc1 was released,
so I guess you should re-do you branch (and pull request) based on
either 4.4-rc1 or Dave's drm-fixes branch.
Heiko
next prev parent reply other threads:[~2015-11-21 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 0:56 [GIT PULL] drm/rockchip: fixes Mark yao
2015-11-21 21:50 ` Heiko Stuebner [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-12-02 2:55 Mark yao
2016-01-22 1:37 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=3016892.vBtLqFySEY@phil \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@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