mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Maxime Ripard <mripard@kernel.org>
To: linux-kernel@vger.kernel.org, "Chen-Yu Tsai" <wens@csie.org>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"David Airlie" <airlied@gmail.com>,
	"Daniel Vetter" <daniel@ffwll.ch>,
	"Jernej Skrabec" <jernej.skrabec@gmail.com>,
	"Samuel Holland" <samuel@sholland.org>,
	"Ondřej Jirman" <megi@xff.cz>
Cc: dri-devel@lists.freedesktop.org,
	linux-arm-kernel@lists.infradead.org,
	 linux-sunxi@lists.linux.dev
Subject: Re: [PATCH v2 0/3] Move blender setup from individual planes to crtc commit in sun4i-drm
Date: Mon, 10 Jun 2024 12:46:11 +0200	[thread overview]
Message-ID: <171801637114.423417.15912541590264684056.b4-ty@kernel.org> (raw)
In-Reply-To: <20240224150604.3855534-1-megi@xff.cz>

On Sat, 24 Feb 2024 16:05:57 +0100, Ondřej Jirman wrote:
> From: Ondrej Jirman <megi@xff.cz>
> 
> This series refactors blender setup from individual planes to a common
> place where it can be performed at once and is easier to reason about.
> 
> In the process this fixes a few bugs that allowed blender pipes to be
> disabled while corresponding DRM planes were requested to be enabled.
> 
> [...]

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

Thanks!
Maxime


  parent reply	other threads:[~2024-06-10 10:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-24 15:05 Ondřej Jirman
2024-02-24 15:05 ` [PATCH v2 1/3] drm/sun4i: Unify sun8i_*_layer structs Ondřej Jirman
2024-02-24 15:05 ` [PATCH v2 2/3] drm/sun4i: Add more parameters to sunxi_engine commit callback Ondřej Jirman
2024-02-24 15:06 ` [PATCH v2 3/3] drm/sun4i: Fix layer zpos change/atomic modesetting Ondřej Jirman
2024-04-19 13:36 ` [PATCH v2 0/3] Move blender setup from individual planes to crtc commit in sun4i-drm Ondřej Jirman
2024-04-21 19:52   ` Jernej Škrabec
2024-06-07 11:54     ` Ondřej Jirman
2024-06-10 10:46 ` Maxime Ripard [this message]
2024-06-10 12:47   ` Ondřej Jirman

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=171801637114.423417.15912541590264684056.b4-ty@kernel.org \
    --to=mripard@kernel.org \
    --cc=airlied@gmail.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=megi@xff.cz \
    --cc=samuel@sholland.org \
    --cc=tzimmermann@suse.de \
    --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®