From: Jani Nikula <jani.nikula@linux.intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/9] A little bit of KMS debug logging tidy
Date: Wed, 27 Apr 2016 13:54:38 +0300 [thread overview]
Message-ID: <87fuu7jp8x.fsf@intel.com> (raw)
In-Reply-To: <1461751622-26927-1-git-send-email-tvrtko.ursulin@linux.intel.com>
On Wed, 27 Apr 2016, Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> wrote:
> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>
> Assorted patches to make the KMS debug logs a bit more
> compact and hence more readable.
Throughout the series I very much dislike the splitting of debug
printing to separate printk() calls. You will get debug output from
elsewhere mixed up in the middle of the drm debug log lines.
BR,
Jani.
>
> Tvrtko Ursulin (9):
> drm: Add drm_mode_debug_printmodeline_raw
> drm: Recognize invalid (all-zero) modes in
> drm_mode_debug_printmodeline(_raw)
> drm/i915: Compact modes in intel_dump_pipe_config
> drm/i915: Tidy planes and scaler info in intel_dump_pipe_config
> drm/i915: Compact intel_dump_pipe_config some more
> drm/i915: Log watermark latencies on a single line per plane
> drm/i915: Compact display clock logging
> drm/i915: Print DisplayPort clocks on a single line
> drm: Quiet down drm_mode_getconnector
>
> drivers/gpu/drm/drm_crtc.c | 2 -
> drivers/gpu/drm/drm_modes.c | 42 +++++++++++---
> drivers/gpu/drm/i915/intel_display.c | 103 ++++++++++++++++++++---------------
> drivers/gpu/drm/i915/intel_dp.c | 33 +++++------
> drivers/gpu/drm/i915/intel_pm.c | 31 ++++++++---
> include/drm/drm_modes.h | 1 +
> 6 files changed, 129 insertions(+), 83 deletions(-)
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-04-27 10:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 10:06 [PATCH 0/9] A little bit of KMS debug logging tidy Tvrtko Ursulin
2016-04-27 10:06 ` [PATCH 1/9] drm: Add drm_mode_debug_printmodeline_raw Tvrtko Ursulin
2016-04-27 12:35 ` Jani Nikula
2016-04-27 12:58 ` Tvrtko Ursulin
2016-04-27 10:06 ` [PATCH 2/9] drm: Recognize invalid (all-zero) modes in drm_mode_debug_printmodeline(_raw) Tvrtko Ursulin
2016-04-27 10:06 ` [PATCH 3/9] drm/i915: Compact modes in intel_dump_pipe_config Tvrtko Ursulin
2016-04-27 12:37 ` Jani Nikula
2016-04-27 10:06 ` [PATCH 4/9] drm/i915: Tidy planes and scaler info " Tvrtko Ursulin
2016-04-27 10:06 ` [PATCH 5/9] drm/i915: Compact intel_dump_pipe_config some more Tvrtko Ursulin
2016-04-27 10:06 ` [PATCH 6/9] drm/i915: Log watermark latencies on a single line per plane Tvrtko Ursulin
2016-04-27 10:07 ` [PATCH 7/9] drm/i915: Compact display clock logging Tvrtko Ursulin
2016-04-27 10:07 ` [PATCH 8/9] drm/i915: Print DisplayPort clocks on a single line Tvrtko Ursulin
2016-04-27 10:07 ` [PATCH 9/9] drm: Quiet down drm_mode_getconnector Tvrtko Ursulin
2016-04-28 8:54 ` Daniel Vetter
2016-04-27 10:54 ` Jani Nikula [this message]
2016-04-27 11:26 ` [PATCH 0/9] A little bit of KMS debug logging tidy Tvrtko Ursulin
2016-04-27 11:57 ` ✗ Fi.CI.BAT: warning for " 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=87fuu7jp8x.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=tvrtko.ursulin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox