dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 0/5] disable drm_global_mutex for most drivers, take 2
Date: Tue, 11 Feb 2020 12:20:00 +0100	[thread overview]
Message-ID: <20200211112000.GA2363188@phenom.ffwll.local> (raw)
In-Reply-To: <61d3ec83-862d-fe88-d618-f7728806ea9a@suse.de>

On Mon, Feb 10, 2020 at 10:47:36AM +0100, Thomas Zimmermann wrote:
> Hi,
> 
> I smoke-tested the patchset by running X11, Weston and fbdev emulation
> on ast and udl. No apparent problems found, so
> 
> Tested-by: Thomas Zimmermann <tzimmermann@suse.de>

Merged patches 2-5 (first one needs to wait for amdgpu/radeon patches),
thanks everyone for review&testing.
-Daniel

> 
> Best regards
> Thomas
> 
> Am 04.02.20 um 16:01 schrieb Daniel Vetter:
> > CI didn't like my test-with tag :-/
> > 
> > Test-with: 20200128112549.172135-1-daniel.vetter@ffwll.ch
> > 
> > Daniel Vetter (5):
> >   drm: Complain if drivers still use the ->load callback
> >   drm/fbdev-helper: don't force restores
> >   drm/client: Rename _force to _locked
> >   drm: Push drm_global_mutex locking in drm_open
> >   drm: Nerf drm_global_mutex BKL for good drivers
> > 
> >  drivers/gpu/drm/drm_client_modeset.c | 12 +++++---
> >  drivers/gpu/drm/drm_drv.c            | 26 +++++++++-------
> >  drivers/gpu/drm/drm_fb_helper.c      | 16 ++--------
> >  drivers/gpu/drm/drm_file.c           | 46 ++++++++++++++++++++++++++--
> >  drivers/gpu/drm/drm_internal.h       |  1 +
> >  include/drm/drm_client.h             |  7 ++++-
> >  include/drm/drm_drv.h                |  3 ++
> >  7 files changed, 79 insertions(+), 32 deletions(-)
> > 
> 
> -- 
> Thomas Zimmermann
> Graphics Driver Developer
> SUSE Software Solutions Germany GmbH
> Maxfeldstr. 5, 90409 Nürnberg, Germany
> (HRB 36809, AG Nürnberg)
> Geschäftsführer: Felix Imendörffer
> 




-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2020-02-11 11:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 15:01 [PATCH 0/5] disable drm_global_mutex for most drivers, take 2 Daniel Vetter
2020-02-04 15:01 ` [PATCH 1/5] drm: Complain if drivers still use the ->load callback Daniel Vetter
2020-02-04 15:01 ` [PATCH 2/5] drm/fbdev-helper: don't force restores Daniel Vetter
2020-02-04 15:01 ` [PATCH 3/5] drm/client: Rename _force to _locked Daniel Vetter
2020-02-04 15:01 ` [PATCH 4/5] drm: Push drm_global_mutex locking in drm_open Daniel Vetter
2020-02-10  8:09   ` Chris Wilson
2020-02-04 15:01 ` [PATCH 5/5] drm: Nerf drm_global_mutex BKL for good drivers Daniel Vetter
2020-02-10  8:09   ` Chris Wilson
2020-02-07 13:37 ` [PATCH 0/5] disable drm_global_mutex for most drivers, take 2 Thomas Zimmermann
2020-02-10  9:47 ` Thomas Zimmermann
2020-02-11 11:20   ` Daniel Vetter [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=20200211112000.GA2363188@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox