From: Maxime Ripard <maxime@cerno.tech>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel.vetter@intel.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/6] drm/vc4: Fixes for the writeback
Date: Fri, 8 Apr 2022 13:41:56 +0200 [thread overview]
Message-ID: <20220408114156.lwdto6qurmm3jikw@houat> (raw)
In-Reply-To: <165a2746-29a7-6749-08d7-f0c7086378ee@suse.de>
[-- Attachment #1: Type: text/plain, Size: 525 bytes --]
On Wed, Apr 06, 2022 at 11:10:12AM +0200, Thomas Zimmermann wrote:
> Hi
>
> Am 28.03.22 um 17:36 schrieb Maxime Ripard:
> > Hi,
> >
> > This series address multiple issues with the transposer support, and thus the
> > writeback support.
>
> With my comments considered, feel free to add
>
> Acked-by: Thomas Zimmermann <tzimmermann@suse.de>
>
> I cannot really check the correctness of the individual HW operations
> though.
I amended the patches with your suggestions and pushed them, thanks!
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2022-04-08 11:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 15:36 [PATCH 0/6] drm/vc4: Fixes for the writeback Maxime Ripard
2022-03-28 15:36 ` [PATCH 1/6] drm/vc4: hvs: Reset muxes at probe time Maxime Ripard
2022-03-28 15:36 ` [PATCH 2/6] drm/vc4: txp: Don't set TXP_VSTART_AT_EOF Maxime Ripard
2022-03-28 15:36 ` [PATCH 3/6] drm/vc4: txp: Force alpha to be 0xff if it's disabled Maxime Ripard
2022-04-06 9:02 ` Thomas Zimmermann
2022-03-28 15:36 ` [PATCH 4/6] drm/vc4: kms: Store channel in local variable Maxime Ripard
2022-03-28 15:36 ` [PATCH 5/6] drm/vc4: kms: Warn if we have an incompatible muxing setup Maxime Ripard
2022-04-06 9:07 ` Thomas Zimmermann
2022-04-08 11:41 ` Maxime Ripard
2022-03-28 15:36 ` [PATCH 6/6] drm/vc4: kms: Improve logging Maxime Ripard
2022-04-06 9:10 ` [PATCH 0/6] drm/vc4: Fixes for the writeback Thomas Zimmermann
2022-04-08 11:41 ` 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=20220408114156.lwdto6qurmm3jikw@houat \
--to=maxime@cerno.tech \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=tzimmermann@suse.de \
/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.