From: Jani Nikula <jani.nikula@linux.intel.com>
To: Wambui Karuga <wambui.karugax@gmail.com>,
joonas.lahtinen@linux.intel.com, rodrigo.vivi@intel.com,
airlied@linux.ie, daniel@ffwll.ch
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 0/8] drm/i915/gt conversion to new drm logging macros.
Date: Thu, 30 Jan 2020 16:07:46 +0200 [thread overview]
Message-ID: <87tv4d9gwd.fsf@intel.com> (raw)
In-Reply-To: <20200128071437.9284-1-wambui.karugax@gmail.com>
On Tue, 28 Jan 2020, Wambui Karuga <wambui.karugax@gmail.com> wrote:
> This series continues the conversion to the new drm logging macros
> focused on the drm/i915/gt folder. This was done both manually and using
> coccinelle.
Thanks for the patches, for now pushed only the non-contentions ones
that don't convert DRM_DEBUG() -> drm_dbg().
BR,
Jani.
>
> Wambui Karuga (8):
> drm/i915/gt: conversion to struct drm_device macros when struct
> drm_i915_private is available.
> drm/i915/ggtt: use new drm logging macros in gt/intel_ggtt.c
> drm/i915/reset: conversion to new drm logging macros in
> gt/intel_reset.c
> drm/i915/engine_cs: use new drm logging macros in gt/intel_engine_cs.c
> drm/i915/lrc: conversion to new drm logging macros in gt/intel_lrc.c
> drm/i915/gt: convert to new logging macros in gt/intel_gt.c
> drm/i915/ring: convert to new logging macros in
> gt/intel_ring_submission.c
> drm/i915/rps: move to new drm logging macros in gt/intel_rps.c
>
> drivers/gpu/drm/i915/gt/intel_engine_cs.c | 11 +--
> drivers/gpu/drm/i915/gt/intel_engine_user.c | 2 +-
> drivers/gpu/drm/i915/gt/intel_ggtt.c | 63 +++++++++------
> drivers/gpu/drm/i915/gt/intel_gt.c | 49 ++++++-----
> drivers/gpu/drm/i915/gt/intel_lrc.c | 24 +++---
> drivers/gpu/drm/i915/gt/intel_rc6.c | 30 ++++---
> drivers/gpu/drm/i915/gt/intel_renderstate.c | 2 +-
> drivers/gpu/drm/i915/gt/intel_reset.c | 48 ++++++-----
> .../gpu/drm/i915/gt/intel_ring_submission.c | 36 +++++----
> drivers/gpu/drm/i915/gt/intel_rps.c | 81 +++++++++----------
> drivers/gpu/drm/i915/gt/intel_workarounds.c | 7 +-
> drivers/gpu/drm/i915/gt/uc/intel_guc_log.c | 3 +-
> drivers/gpu/drm/i915/gt/uc/intel_uc.c | 4 +-
> 13 files changed, 196 insertions(+), 164 deletions(-)
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2020-01-30 14:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 7:14 [Intel-gfx] [PATCH 0/8] drm/i915/gt conversion to new drm logging macros Wambui Karuga
2020-01-28 7:14 ` [Intel-gfx] [PATCH 1/8] drm/i915/gt: conversion to struct drm_device macros when struct drm_i915_private is available Wambui Karuga
2020-01-28 7:14 ` [Intel-gfx] [PATCH 2/8] drm/i915/ggtt: use new drm logging macros in gt/intel_ggtt.c Wambui Karuga
2020-01-28 7:14 ` [Intel-gfx] [PATCH 3/8] drm/i915/reset: conversion to new drm logging macros in gt/intel_reset.c Wambui Karuga
2020-01-28 7:14 ` [Intel-gfx] [PATCH 4/8] drm/i915/engine_cs: use new drm logging macros in gt/intel_engine_cs.c Wambui Karuga
2020-01-28 7:14 ` [Intel-gfx] [PATCH 5/8] drm/i915/lrc: conversion to new drm logging macros in gt/intel_lrc.c Wambui Karuga
2020-01-28 7:14 ` [Intel-gfx] [PATCH 6/8] drm/i915/gt: convert to new logging macros in gt/intel_gt.c Wambui Karuga
2020-01-28 7:14 ` [Intel-gfx] [PATCH 7/8] drm/i915/ring: convert to new logging macros in gt/intel_ring_submission.c Wambui Karuga
2020-01-28 7:14 ` [Intel-gfx] [PATCH 8/8] drm/i915/rps: move to new drm logging macros in gt/intel_rps.c Wambui Karuga
2020-01-28 7:42 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/gt conversion to new drm logging macros Patchwork
2020-01-29 6:57 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-01-30 14:07 ` Jani Nikula [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=87tv4d9gwd.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=wambui.karugax@gmail.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