All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 0/4] drm/i915: Per-device display tracepoints
Date: Fri, 11 Nov 2022 17:31:07 +0200	[thread overview]
Message-ID: <87leoh4if8.fsf@intel.com> (raw)
In-Reply-To: <20221111123120.7759-1-ville.syrjala@linux.intel.com>

On Fri, 11 Nov 2022, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Resurrect my old patch to include the device name in the display
> tracepoints. Seems like a good with discrete GPUs being a thing.

FWIW, on the series,

Acked-by: Jani Nikula <jani.nikula@intel.com>



>
> Ville Syrjälä (4):
>   drm/i915: Pass intel_plane to plane tracepoints
>   drm/i915: Print plane name in fbc tracepoints
>   drm/i915: Pass i915 to frontbuffer tracepoints
>   drm/i915: Add device name to display tracepoints
>
>  .../gpu/drm/i915/display/intel_atomic_plane.c |   6 +-
>  .../drm/i915/display/intel_display_trace.h    | 206 ++++++++++++------
>  .../gpu/drm/i915/display/intel_frontbuffer.c  |   4 +-
>  3 files changed, 140 insertions(+), 76 deletions(-)

-- 
Jani Nikula, Intel Open Source Graphics Center

  parent reply	other threads:[~2022-11-11 15:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11 12:31 [Intel-gfx] [PATCH 0/4] drm/i915: Per-device display tracepoints Ville Syrjala
2022-11-11 12:31 ` [Intel-gfx] [PATCH 1/4] drm/i915: Pass intel_plane to plane tracepoints Ville Syrjala
2022-11-11 12:31 ` [Intel-gfx] [PATCH 2/4] drm/i915: Print plane name in fbc tracepoints Ville Syrjala
2022-11-11 12:31 ` [Intel-gfx] [PATCH 3/4] drm/i915: Pass i915 to frontbuffer tracepoints Ville Syrjala
2022-11-11 12:31 ` [Intel-gfx] [PATCH 4/4] drm/i915: Add device name to display tracepoints Ville Syrjala
2022-11-11 12:52 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Per-device " Patchwork
2022-11-11 13:21 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-11-11 15:31 ` Jani Nikula [this message]
2022-11-11 18:54 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Per-device display tracepoints (rev2) Patchwork
2022-11-11 19:14 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-11-12 11:32 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=87leoh4if8.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@linux.intel.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 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.