All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime@cerno.tech>
To: dri-devel@lists.freedesktop.org, Maxime Ripard <maxime@cerno.tech>
Cc: David Airlie <airlied@linux.ie>,
	Daniel Vetter <daniel.vetter@intel.com>,
	Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: [PATCH v2 0/7] drm/vc4: hvs: Various improvements
Date: Wed,  6 Apr 2022 15:26:28 +0200	[thread overview]
Message-ID: <164925158504.1310811.6236787289249011628.b4-ty@cerno.tech> (raw)
In-Reply-To: <20220331143744.777652-1-maxime@cerno.tech>

On Thu, 31 Mar 2022 16:37:37 +0200, Maxime Ripard wrote:
> These patches used to be part of the series:
> https://lore.kernel.org/all/20220221134155.125447-1-maxime@cerno.tech/
> 
> but since the main patch got superseded by another core patch, I've split the
> cleanup patches out into their own series.
> 
> Let me know what you think,
> Maxime
> 
> [...]

Applied to drm/drm-misc (drm-misc-next).

Thanks!
Maxime

      parent reply	other threads:[~2022-04-06 13:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31 14:37 [PATCH v2 0/7] drm/vc4: hvs: Various improvements Maxime Ripard
2022-03-31 14:37 ` [PATCH v2 1/7] drm/vc4: kms: Take old state core clock rate into account Maxime Ripard
2022-03-31 14:37 ` [PATCH v2 2/7] drm/vc4: hvs: Fix frame count register readout Maxime Ripard
2022-03-31 14:37 ` [PATCH v2 3/7] drm/vc4: hvs: Store channel in variable Maxime Ripard
2022-03-31 14:37 ` [PATCH v2 4/7] drm/vc4: hvs: Remove dlist setup duplication Maxime Ripard
2022-03-31 14:37 ` [PATCH v2 5/7] drm/vc4: hvs: Move the dlist setup to its own function Maxime Ripard
2022-04-06 10:41   ` Thomas Zimmermann
2022-03-31 14:37 ` [PATCH v2 6/7] drm/vc4: kms: Ignore atomic_flush if we're disabled Maxime Ripard
2022-03-31 14:37 ` [PATCH v2 7/7] drm/vc4: hvs: Use pointer to HVS in HVS_READ and HVS_WRITE macros Maxime Ripard
2022-04-06 10:44 ` [PATCH v2 0/7] drm/vc4: hvs: Various improvements Thomas Zimmermann
2022-04-06 13:26 ` 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=164925158504.1310811.6236787289249011628.b4-ty@cerno.tech \
    --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.