All of lore.kernel.org
 help / color / mirror / Atom feed
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/7] drm/i915/gt: convert to struct drm_device based logging macros.
Date: Thu, 19 Mar 2020 11:54:12 +0200	[thread overview]
Message-ID: <874kukekl7.fsf@intel.com> (raw)
In-Reply-To: <20200314183344.17603-1-wambui.karugax@gmail.com>

On Sat, 14 Mar 2020, Wambui Karuga <wambui.karugax@gmail.com> wrote:
> This patchset continues the conversion of printk based macros to use
> the struct drm_device based drm logging macros focused on the i915/gt
> folder.
> These patches were achieved using both coccinelle and manually.

Pushed the lot, thanks for the patches.

BR,
Jani.

>
> Wambui Karuga (7):
>   drm/i915/ggtt: convert to drm_device based logging macros.
>   drm/i915/lrc: convert to struct drm_device based logging macros.
>   drm/i915/rc6: convert to struct drm_device based logging macros.
>   drm/i915/renderstate: use struct drm_device based logging macros.
>   drm/i915/ring_submission: use drm_device based logging macros.
>   drm/i915/rps: use struct drm_device based logging macros.
>   drm/i915/workarounds: convert to drm_device based logging macros.
>
>  drivers/gpu/drm/i915/gt/intel_ggtt.c          | 38 ++++++----
>  drivers/gpu/drm/i915/gt/intel_lrc.c           | 14 ++--
>  drivers/gpu/drm/i915/gt/intel_rc6.c           | 35 +++++----
>  drivers/gpu/drm/i915/gt/intel_renderstate.c   |  2 +-
>  .../gpu/drm/i915/gt/intel_ring_submission.c   | 33 ++++----
>  drivers/gpu/drm/i915/gt/intel_rps.c           | 75 +++++++++----------
>  drivers/gpu/drm/i915/gt/intel_workarounds.c   |  7 +-
>  7 files changed, 110 insertions(+), 94 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

      parent reply	other threads:[~2020-03-19  9:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-14 18:33 [Intel-gfx] [PATCH 0/7] drm/i915/gt: convert to struct drm_device based logging macros Wambui Karuga
2020-03-14 18:33 ` [Intel-gfx] [PATCH 1/7] drm/i915/ggtt: convert to " Wambui Karuga
2020-03-14 18:33 ` [Intel-gfx] [PATCH 2/7] drm/i915/lrc: convert to struct " Wambui Karuga
2020-03-14 18:33 ` [Intel-gfx] [PATCH 3/7] drm/i915/rc6: " Wambui Karuga
2020-03-14 18:33 ` [Intel-gfx] [PATCH 4/7] drm/i915/renderstate: use " Wambui Karuga
2020-03-14 18:33 ` [Intel-gfx] [PATCH 5/7] drm/i915/ring_submission: use " Wambui Karuga
2020-03-14 18:33 ` [Intel-gfx] [PATCH 6/7] drm/i915/rps: use struct " Wambui Karuga
2020-03-14 18:33 ` [Intel-gfx] [PATCH 7/7] drm/i915/workarounds: convert to " Wambui Karuga
2020-03-16 16:16 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/gt: convert to struct " Patchwork
2020-03-16 16:49 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-03-17  0:01 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-03-19  9:54 ` 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=874kukekl7.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 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.