From: Sam Ravnborg <sam@ravnborg.org>
To: Paul Cercueil <paul@crapouillou.net>
Cc: David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Christophe Branchereau <cbranchereau@gmail.com>,
list@opendingux.net, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org
Subject: Re: [PATCH 0/6] drm/ingenic: JZ4760(B) support and random changes
Date: Sat, 9 Jul 2022 10:31:45 +0200 [thread overview]
Message-ID: <Ysk88cZO1iQhX/I2@ravnborg.org> (raw)
In-Reply-To: <20220708205406.96473-1-paul@crapouillou.net>
Hi Paul,
On Fri, Jul 08, 2022 at 09:54:00PM +0100, Paul Cercueil wrote:
> Hi,
>
> A small set of changes to the ingenic-drm driver.
>
> The most notable thing is that ingenic-ipu is now its own platform
> driver.
It would be nice to know what is achieved by this change, I could
see the code being a tad simpler, but the cost was more EXPORTs.
With the added explanation, which you can add when applying, all patches are:
Acked-by: Sam Ravnborg <sam@ravnborg.org>
Sam
next prev parent reply other threads:[~2022-07-09 8:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 20:54 Paul Cercueil
2022-07-08 20:54 ` [PATCH 1/6] dt-bindings/display: ingenic: Add compatible string for the JZ4760(B) Paul Cercueil
2022-07-10 14:43 ` Krzysztof Kozlowski
2022-07-08 20:54 ` [PATCH 2/6] drm/ingenic: Fix MODULE_LICENSE() string Paul Cercueil
2022-07-08 20:54 ` [PATCH 3/6] drm/ingenic: Add support for the JZ4760(B) Paul Cercueil
2022-07-08 20:54 ` [PATCH 4/6] drm/ingenic: Don't request full modeset if property is not modified Paul Cercueil
2022-07-08 20:54 ` [PATCH 5/6] drm/ingenic: Make IPU driver its own module Paul Cercueil
2022-07-08 20:54 ` [PATCH 6/6] drm/ingenic: Use the new PM macros Paul Cercueil
2022-07-09 8:31 ` Sam Ravnborg [this message]
2022-07-09 10:43 ` [PATCH 0/6] drm/ingenic: JZ4760(B) support and random changes Paul Cercueil
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=Ysk88cZO1iQhX/I2@ravnborg.org \
--to=sam@ravnborg.org \
--cc=airlied@linux.ie \
--cc=cbranchereau@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=list@opendingux.net \
--cc=paul@crapouillou.net \
/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®