All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: airlied@linux.ie, dri-devel@lists.freedesktop.org,
	maarten.lankhorst@linux.intel.com, mripard@kernel.org,
	virtualization@lists.linux-foundation.org, noralf@tronnes.org,
	daniel@ffwll.ch, alexander.deucher@amd.com,
	spice-devel@lists.freedesktop.org, emil.velikov@collabora.com
Subject: Re: [PATCH v4 0/4] drm: Provide a simple encoder
Date: Fri, 28 Feb 2020 20:36:03 +0100	[thread overview]
Message-ID: <20200228193603.GA22966@ravnborg.org> (raw)
In-Reply-To: <20200228081828.18463-1-tzimmermann@suse.de>

Hi Thomas.

On Fri, Feb 28, 2020 at 09:18:24AM +0100, Thomas Zimmermann wrote:
> Many DRM drivers implement an encoder with an empty implementation. This
> patchset adds drm_simple_encoder_init(), which drivers can use instead.
> Except for the destroy callback, the simple encoder's implementation is
> empty.
> 
> The patchset also converts 4 encoder instances to use the simple-encoder
> helpers. But there are at least 11 other drivers which can use the helper
> and I think I did not examine all drivers yet.
> 
> The patchset was smoke-tested on mgag200 by running the fbdev console
> and Gnome on X11.
> 
> v4:
> 	* print error messages with drm_err() (Sam)
> 	* qxl: handle errors of drm_simple_encoder_init() (Sam)

Looked through the patches - all looked good.
IMO ready to apply.

	Sam

WARNING: multiple messages have this Message-ID (diff)
From: Sam Ravnborg <sam@ravnborg.org>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: airlied@linux.ie, dri-devel@lists.freedesktop.org,
	virtualization@lists.linux-foundation.org, kraxel@redhat.com,
	alexander.deucher@amd.com, spice-devel@lists.freedesktop.org,
	emil.velikov@collabora.com
Subject: Re: [PATCH v4 0/4] drm: Provide a simple encoder
Date: Fri, 28 Feb 2020 20:36:03 +0100	[thread overview]
Message-ID: <20200228193603.GA22966@ravnborg.org> (raw)
In-Reply-To: <20200228081828.18463-1-tzimmermann@suse.de>

Hi Thomas.

On Fri, Feb 28, 2020 at 09:18:24AM +0100, Thomas Zimmermann wrote:
> Many DRM drivers implement an encoder with an empty implementation. This
> patchset adds drm_simple_encoder_init(), which drivers can use instead.
> Except for the destroy callback, the simple encoder's implementation is
> empty.
> 
> The patchset also converts 4 encoder instances to use the simple-encoder
> helpers. But there are at least 11 other drivers which can use the helper
> and I think I did not examine all drivers yet.
> 
> The patchset was smoke-tested on mgag200 by running the fbdev console
> and Gnome on X11.
> 
> v4:
> 	* print error messages with drm_err() (Sam)
> 	* qxl: handle errors of drm_simple_encoder_init() (Sam)

Looked through the patches - all looked good.
IMO ready to apply.

	Sam
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-02-28 19:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-28  8:18 [PATCH v4 0/4] drm: Provide a simple encoder Thomas Zimmermann
2020-02-28  8:18 ` Thomas Zimmermann
2020-02-28  8:18 ` [PATCH v4 1/4] drm/simple-kms: Add drm_simple_encoder_{init, create}() Thomas Zimmermann
2020-02-28  8:18   ` Thomas Zimmermann
2020-02-28  8:18 ` [PATCH v4 2/4] drm/ast: Use simple encoder Thomas Zimmermann
2020-02-28  8:18   ` Thomas Zimmermann
2020-02-28  8:18 ` [PATCH v4 3/4] drm/mgag200: " Thomas Zimmermann
2020-02-28  8:18   ` Thomas Zimmermann
2020-02-28  8:18 ` [PATCH v4 4/4] drm/qxl: " Thomas Zimmermann
2020-02-28  8:18   ` Thomas Zimmermann
2020-02-28 19:36 ` Sam Ravnborg [this message]
2020-02-28 19:36   ` [PATCH v4 0/4] drm: Provide a " Sam Ravnborg

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=20200228193603.GA22966@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=airlied@linux.ie \
    --cc=alexander.deucher@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.velikov@collabora.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=noralf@tronnes.org \
    --cc=spice-devel@lists.freedesktop.org \
    --cc=tzimmermann@suse.de \
    --cc=virtualization@lists.linux-foundation.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 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.