public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: "Chris Wilson" <chris@chris-wilson.co.uk>,
	"Daniel Vetter" <daniel.vetter@ffwll.ch>,
	"DRI Development" <dri-devel@lists.freedesktop.org>,
	"Intel Graphics Development" <intel-gfx@lists.freedesktop.org>,
	"Jyri Sarha" <jsarha@ti.com>,
	"Russell King" <rmk+kernel@armlinux.org.uk>,
	"Tomi Valkeinen" <tomi.valkeinen@ti.com>,
	"Thierry Reding" <thierry.reding@gmail.com>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Daniel Vetter" <daniel.vetter@intel.com>,
	"Christian König" <christian.koenig@amd.com>,
	"Lucas Stach" <l.stach@pengutronix.de>
Subject: Re: [PATCH] drm/mm: Convert to drm_printer
Date: Thu, 29 Dec 2016 13:38:51 +0100	[thread overview]
Message-ID: <20161229123851.GC26729@dvetter-linux.ger.corp.intel.com> (raw)
In-Reply-To: <20161229113145.GB13154@nuc-i3427.alporthouse.com>

On Thu, Dec 29, 2016 at 11:31:45AM +0000, Chris Wilson wrote:
> On Thu, Dec 29, 2016 at 12:09:24PM +0100, Daniel Vetter wrote:
> > Including all drivers. I thought about keeping small compat functions
> > to avoid having to change all drivers. But I really like the
> > drm_printer idea, so figured spreading it more widely is a good thing.
> > 
> > v2: Review from Chris:
> > - Natural argument order and better name for drm_mm_print.
> > - show_mm() macro in the selftest.
> > 
> > Cc: Rob Clark <robdclark@gmail.com>
> > Cc: Russell King <rmk+kernel@armlinux.org.uk>
> > Cc: Alex Deucher <alexander.deucher@amd.com>
> > Cc: Christian König <christian.koenig@amd.com>
> > Cc: Lucas Stach <l.stach@pengutronix.de>
> > Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>
> > Cc: Thierry Reding <thierry.reding@gmail.com>
> > Cc: Jyri Sarha <jsarha@ti.com>
> > Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
> 
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>

r-b on both patches?
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-12-29 12:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-28 16:42 [PATCH 1/2] drm/printer: add debug printer Daniel Vetter
2016-12-28 16:42 ` [PATCH 2/2] drm/mm: Convert to drm_printer Daniel Vetter
2016-12-28 17:01   ` Chris Wilson
2016-12-29 11:09   ` [PATCH] " Daniel Vetter
2016-12-29 11:31     ` Chris Wilson
2016-12-29 12:38       ` Daniel Vetter [this message]
2016-12-28 17:23 ` ✗ Fi.CI.BAT: warning for series starting with [1/2] drm/printer: add debug printer Patchwork
2016-12-29 11:53 ` ✓ Fi.CI.BAT: success for series starting with [1/2] drm/printer: add debug printer (rev2) Patchwork
2016-12-29 12:47 ` [PATCH 1/2] drm/printer: add debug printer Chris Wilson
2016-12-30 10:42   ` Daniel Vetter

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=20161229123851.GC26729@dvetter-linux.ger.corp.intel.com \
    --to=daniel@ffwll.ch \
    --cc=alexander.deucher@amd.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=christian.koenig@amd.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jsarha@ti.com \
    --cc=l.stach@pengutronix.de \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=thierry.reding@gmail.com \
    --cc=tomi.valkeinen@ti.com \
    /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