From: Stefan Monnier <monnier@iro.umontreal.ca>
To: linux-clk@vger.kernel.org
Cc: linux-sunxi@googlegroups.com, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 4/8] drm/sun4i: add support for sun8i DE2 mixers and display engines
Date: Thu, 23 Feb 2017 09:27:38 -0500 [thread overview]
Message-ID: <jwvwpchgez7.fsf-monnier+gmane.comp.hardware.netbook.arm.sunxi@gnu.org> (raw)
In-Reply-To: 20170222151854.3280-5-icenowy@aosc.xyz
> drivers/gpu/drm/sun4i/Kconfig | 8 +
> drivers/gpu/drm/sun4i/Makefile | 1 +
> drivers/gpu/drm/sun4i/sun4i_crtc.c | 6 +-
> drivers/gpu/drm/sun4i/sun4i_drv.c | 38 +++-
> drivers/gpu/drm/sun4i/sun4i_drv.h | 1 +
> drivers/gpu/drm/sun4i/sun4i_layer.c | 92 ++++++--
> drivers/gpu/drm/sun4i/sun4i_layer.h | 1 +
> drivers/gpu/drm/sun4i/sun8i_mixer.c | 417 ++++++++++++++++++++++++++++++++++++
> drivers/gpu/drm/sun4i/sun8i_mixer.h | 133 ++++++++++++
Should the drm/sun4i directory be renamed to drm/sunxi then?
Stefan
next prev parent reply other threads:[~2017-02-23 15:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 15:18 [PATCH 0/8] Initial Allwinner Display Engine 2.0 Support Icenowy Zheng
2017-02-22 15:18 ` [PATCH 1/8] dt-bindings: add binding for the Allwinner DE2 CCU Icenowy Zheng
2017-02-22 15:18 ` [PATCH 2/8] clk: sunxi-ng: add support for " Icenowy Zheng
2017-02-22 19:09 ` Maxime Ripard
2017-02-22 15:18 ` [PATCH 3/8] dt-bindings: add bindings for DE2 on V3s SoC Icenowy Zheng
2017-02-22 15:18 ` [PATCH 4/8] drm/sun4i: add support for sun8i DE2 mixers and display engines Icenowy Zheng
2017-02-22 22:01 ` Jernej Škrabec
2017-02-22 22:04 ` Icenowy Zheng
2017-02-23 14:27 ` Stefan Monnier [this message]
2017-02-23 17:44 ` Emil Velikov
2017-02-24 0:46 ` Maxime Ripard
-- strict thread matches above, loose matches on Subject: below --
2017-02-22 15:23 Icenowy Zheng
2017-02-22 20:09 ` Maxime Ripard
2017-02-22 20:28 ` Icenowy Zheng
2017-02-22 22:54 ` Maxime Ripard
2017-02-24 13:30 ` Rob Herring
2017-02-24 15:30 ` Jernej Škrabec
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=jwvwpchgez7.fsf-monnier+gmane.comp.hardware.netbook.arm.sunxi@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
/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