From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Chen-Yu Tsai <wens@csie.org>
Cc: David Airlie <airlied@linux.ie>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com
Subject: Re: [PATCH 0/3] drm/sun4i: More cleanups and fixes
Date: Wed, 26 Apr 2017 08:21:26 +0200 [thread overview]
Message-ID: <20170426062126.e2g6sqr42ytqfg3g@lukather> (raw)
In-Reply-To: <20170425152505.6796-1-wens@csie.org>
[-- Attachment #1: Type: text/plain, Size: 629 bytes --]
On Tue, Apr 25, 2017 at 11:25:02PM +0800, Chen-Yu Tsai wrote:
> Hi Maxime,
>
> The subject is probably getting old. Here are a few more cleanups.
>
> Patch 1 should have been part of the patch
>
> drm/sun4i: Use lists to track registered display backends and TCONs
>
> from my multiple pipeline support series. Please squash it in if you can.
>
> Patch 2 just moves setting the TCON clocks back inside the TCON driver.
>
> Patch 3 cleans up a DRM driver debug message.
Applied all, thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
prev parent reply other threads:[~2017-04-26 6:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 15:25 Chen-Yu Tsai
2017-04-25 15:25 ` [PATCH 1/3] drm/sun4i: Drop unused tcon pointer Chen-Yu Tsai
2017-04-25 15:25 ` [PATCH 2/3] drm/sun4i: Set TCON clock inside sun4i_tconX_mode_set Chen-Yu Tsai
2017-04-25 15:25 ` [PATCH 3/3] drm/sun4i: backend: Clarify sun4i_backend_layer_enable debug message Chen-Yu Tsai
2017-04-26 6:21 ` Maxime Ripard [this message]
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=20170426062126.e2g6sqr42ytqfg3g@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=airlied@linux.ie \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=wens@csie.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
all inboxes | Powered by JetHome®