Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [CI 1/6] drm/printer: Add drm_vprintf()
Date: Thu, 23 Nov 2017 12:36:40 +0200	[thread overview]
Message-ID: <1511433400.4641.23.camel@linux.intel.com> (raw)
In-Reply-To: <151142916658.29492.641924665866797178@mail.alporthouse.com>

On Thu, 2017-11-23 at 09:26 +0000, Chris Wilson wrote:
> Quoting Chris Wilson (2017-11-23 08:40:46)
> > Simple va_args equivalent to the existing drm_printf() for use with the
> > drm_printer.
> > 
> > v2: Fixup kerneldoc to match final parameter names.
> > v3: Turn it into a kerneldoc comment
> > 
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Rob Clark <robdclark@gmail.com>
> > Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> > Cc: Dave Airlie <airlied@redhat.com>
> > Acked-by: Dave Airlie <airlied@redhat.com>
> 
> Ok, this doesn't apply to drm-intel-next-queued any more, it may as well
> go to drm-misc and I'll wait for the backmerge.

Applied to drm-misc-next. Thanks for the patch and review.

Regards, Joonas
-- 
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-11-23 10:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-23  8:40 [CI 1/6] drm/printer: Add drm_vprintf() Chris Wilson
2017-11-23  8:40 ` [CI 2/6] drm/i915: Use snprintf to avoid line-break when pretty-printing engines Chris Wilson
2017-11-23  8:40 ` [CI 3/6] drm/i915: Make engine state pretty-printer header configurable Chris Wilson
2017-11-23  8:40 ` [CI 4/6] drm/i915: Include engine state on detecting a missed breadcrumb/seqno Chris Wilson
2017-11-23  8:40 ` [CI 5/6] drm/i915: Include the global reset count for intel_engine_dump() Chris Wilson
2017-11-23  8:40 ` [CI 6/6] drm/i915: Add is-wedged flag to intel_engine_dump() Chris Wilson
2017-11-23  9:18 ` ✓ Fi.CI.BAT: success for series starting with [CI,1/6] drm/printer: Add drm_vprintf() Patchwork
2017-11-23  9:26 ` [CI 1/6] " Chris Wilson
2017-11-23 10:36   ` Joonas Lahtinen [this message]
2017-11-23 12:01 ` ✓ Fi.CI.IGT: success for series starting with [CI,1/6] " Patchwork

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=1511433400.4641.23.camel@linux.intel.com \
    --to=joonas.lahtinen@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox