From: Xinliang Liu <xinliang.liu@linaro.org>
To: Dave Airlie <airlied@gmail.com>
Cc: Peter Griffin <peter.griffin@linaro.org>,
Guodong Xu <guodong.xu@linaro.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: [GIT PULL] drm-hisilicon-next
Date: Tue, 29 Aug 2017 10:46:33 +0800 [thread overview]
Message-ID: <CAGd==0523AQRmfe2=B5k2bDEm10V3PbYNtjM=GrODssOje8Qug@mail.gmail.com> (raw)
Hi Dave,
One fix for next.
Sorry for late pull request. If it can't catch this round, will resend
on next round.
Best,
Xinliang
The following changes since commit 7846b12fe0b5feab5446d892f41b5140c1419109:
Merge branch 'drm-vmwgfx-next' of
git://people.freedesktop.org/~syeh/repos_linux into drm-next
(2017-08-29 10:38:14 +1000)
are available in the git repository at:
git@github.com:xin3liang/linux.git tags/drm-hisilicon-next-2017-08-29
for you to fetch changes up to 834fe0f6023a4fad68612dbbe93866c4df32142e:
drm/hisilicon: Ensure LDI regs are properly configured. (2017-08-29
10:17:18 +0800)
----------------------------------------------------------------
hisilicon-drm-next
----------------------------------------------------------------
Peter Griffin (1):
drm/hisilicon: Ensure LDI regs are properly configured.
drivers/gpu/drm/hisilicon/kirin/kirin_drm_ade.c | 3 +++
1 file changed, 3 insertions(+)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-08-29 2:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 2:46 Xinliang Liu [this message]
2017-08-29 8:32 ` [GIT PULL] drm-hisilicon-next Daniel Vetter
2017-08-29 9:54 ` Xinliang Liu
2017-08-29 13:57 ` Daniel Vetter
2017-08-30 5:57 ` Xinliang Liu
2017-08-30 7:41 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2017-11-01 2:51 Xinliang Liu
2016-07-04 11:09 Xinliang Liu
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='CAGd==0523AQRmfe2=B5k2bDEm10V3PbYNtjM=GrODssOje8Qug@mail.gmail.com' \
--to=xinliang.liu@linaro.org \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=guodong.xu@linaro.org \
--cc=peter.griffin@linaro.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.