All of lore.kernel.org
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javierm@redhat.com>
To: Thomas Zimmermann <tzimmermann@suse.de>, linux-kernel@vger.kernel.org
Cc: David Airlie <airlied@linux.ie>, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/ssd130x: Use drm_atomic_get_new_plane_state()
Date: Tue, 27 Sep 2022 13:36:10 +0200	[thread overview]
Message-ID: <fed13d05-999a-8c31-78d6-cd5efbe2a64e@redhat.com> (raw)
In-Reply-To: <8a974e5a-949a-5eb8-4f01-64e6114dafa7@suse.de>

On 9/26/22 09:24, Thomas Zimmermann wrote:
> 
> 
> Am 23.09.22 um 10:34 schrieb Javier Martinez Canillas:
>> The struct drm_plane .state shouldn't be accessed directly but instead the
>> drm_atomic_get_new_plane_state() helper function should be used.
>>
>> This is based on a similar patch from Thomas Zimmermann for the simpledrm
>> driver. No functional changes.
>>
>> Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>> Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
> 
> Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>
> 

Pushed to drm-misc (drm-misc-next). Thanks!

-- 
Best regards,

Javier Martinez Canillas
Core Platforms
Red Hat


      reply	other threads:[~2022-09-27 11:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23  8:34 [PATCH] drm/ssd130x: Use drm_atomic_get_new_plane_state() Javier Martinez Canillas
2022-09-23  8:34 ` Javier Martinez Canillas
2022-09-23  9:05 ` Ville Syrjälä
2022-09-23  9:05   ` Ville Syrjälä
2022-09-23  9:16   ` Javier Martinez Canillas
2022-09-23  9:16     ` Javier Martinez Canillas
2022-09-23  9:43     ` Ville Syrjälä
2022-09-23  9:43       ` Ville Syrjälä
2022-09-26  7:24 ` Thomas Zimmermann
2022-09-27 11:36   ` 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=fed13d05-999a-8c31-78d6-cd5efbe2a64e@redhat.com \
    --to=javierm@redhat.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.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 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.