From: Javier Martinez Canillas <javierm@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Thomas Zimmermann <tzimmermann@suse.de>,
Daniel Vetter <daniel@ffwll.ch>, Dave Airlie <airlied@redhat.com>,
David Airlie <airlied@linux.ie>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 0/4] Add a drm_crtc_helper_atomic_check() helper
Date: Thu, 13 Oct 2022 09:34:25 +0200 [thread overview]
Message-ID: <b5e30da4-d958-4227-6e13-07f58ea0ccb8@redhat.com> (raw)
In-Reply-To: <20221011165136.469750-1-javierm@redhat.com>
On 10/11/22 18:51, Javier Martinez Canillas wrote:
> Add a helper function and make drivers that have the same logic in their
> struct drm_crtc_helper_funcs .atomic_check handler to use this instead.
>
> Patch #1, #2 and #3 are just cleanups for the mgag200, simpledrm and
> ssd130x drivers respectively. Finally patch #4 converts the last two
> drivers to use a helper instead of open coding it the same logic.
>
> The changes are inspired by a patch from Thomas Zimmermann for the ast
> DRM driver:
>
> https://patchwork.kernel.org/project/dri-devel/patch/20221010103625.19958-4-tzimmermann@suse.de/
>
> This is a v2 that addresses issues pointed out also by Thomas in v1:
>
Pushed this to drm-misc (drm-misc-next). Thanks!
--
Best regards,
Javier Martinez Canillas
Core Platforms
Red Hat
prev parent reply other threads:[~2022-10-13 7:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 16:51 Javier Martinez Canillas
2022-10-11 16:51 ` [PATCH v2 1/4] drm/mgag200: Do not call drm_atomic_add_affected_planes() Javier Martinez Canillas
2022-10-12 7:28 ` Thomas Zimmermann
2022-10-11 16:51 ` [PATCH v2 2/4] drm/simpledrm: " Javier Martinez Canillas
2022-10-11 16:51 ` [PATCH v2 3/4] drm/ssd130x: " Javier Martinez Canillas
2022-10-11 16:51 ` [PATCH v2 4/4] drm/crtc-helper: Add a drm_crtc_helper_atomic_check() helper Javier Martinez Canillas
2022-10-13 7:34 ` Javier Martinez Canillas [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=b5e30da4-d958-4227-6e13-07f58ea0ccb8@redhat.com \
--to=javierm@redhat.com \
--cc=airlied@linux.ie \
--cc=airlied@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.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 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®