From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: "airlied@gmail.com" <airlied@gmail.com>
Cc: Carlos Palminha <CARLOS.PALMINHA@synopsys.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"daniel.vetter@intel.com" <daniel.vetter@intel.com>,
Jose Abreu <Jose.Abreu@synopsys.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>
Subject: Please pull ARCPGU changes
Date: Mon, 31 Jul 2017 11:11:06 +0000 [thread overview]
Message-ID: <1501499465.6216.4.camel@synopsys.com> (raw)
Hi Dave,
Could you please pull a couple of minor fixes for ARCPGU.
These changes are based on today's drm-misc/drm-misc-next.
The following changes since commit 9dd2aca46a13cc7177625f0dc3aaf5b7ebc6fe74:
drm/rockchip: vop: rk3328: fix overlay abnormal (2017-07-31 08:44:18 +0800)
are available in the git repository at:
https://github.com/foss-for-synopsys-dwc-arc-processors/linux topic-arcpgu-updates
for you to fetch changes up to a8709950755748e9975d63faa624f2ba4b39f9d6:
drm: arcpgu: Allow some clock deviation in crtc->mode_valid() callback (2017-07-31 14:05:21 +0300)
----------------------------------------------------------------
Alexey Brodkin (2):
drm/arcpgu: Opt in debugfs
arcpgu: Simplify driver name
Jose Abreu (3):
drm: arcpgu: Fix mmap() callback
drm: arcpgu: Fix module unload
drm: arcpgu: Allow some clock deviation in crtc->mode_valid() callback
drivers/gpu/drm/arc/arcpgu_crtc.c | 7 ++++---
drivers/gpu/drm/arc/arcpgu_drv.c | 57 ++++++++++++++++++++++++++++++++-------------------------
2 files changed, 36 insertions(+), 28 deletions(-)
Regards,
Alexey
next reply other threads:[~2017-07-31 11:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 11:11 Alexey Brodkin [this message]
2017-08-02 9:41 ` Please pull ARCPGU changes Daniel Vetter
2017-08-02 10:16 ` Alexey Brodkin
2017-08-02 18:24 ` Alex Deucher
2017-08-02 21:21 ` Alexey Brodkin
2017-08-02 21:20 ` [PULL] " Alexey Brodkin
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=1501499465.6216.4.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=CARLOS.PALMINHA@synopsys.com \
--cc=Jose.Abreu@synopsys.com \
--cc=airlied@gmail.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@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