From: Wambui Karuga <wambui.karugax@gmail.com>
To: jani.nikula@linux.intel.com, joonas.lahtinen@linux.intel.com,
rodrigo.vivi@intel.com, airlied@linux.ie, daniel@ffwll.ch
Cc: sean@poorly.run, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] Use new logging macros in drm/i915
Date: Thu, 9 Jan 2020 12:06:41 +0300 [thread overview]
Message-ID: <cover.1578560355.git.wambui.karugax@gmail.com> (raw)
This patchset continues the conversion to using the new struct
drm_device based logging macros in drm/i915.
Wambui Karuga (5):
drm/i915: conversion to new logging macros in i915/i915_vgpu.c
drm/i915: conversion to new logging macros in i915/intel_csr.c
drm/i915: conversion to new logging macros in i915/intel_device_info.c
drm/i915: convert to new logging macros in i915/intel_gvt.c
drm/i915: convert to new logging macros in i915/intel_memory_region.c
drivers/gpu/drm/i915/i915_vgpu.c | 41 +++++++++++++---------
drivers/gpu/drm/i915/intel_csr.c | 24 +++++++------
drivers/gpu/drm/i915/intel_device_info.c | 25 +++++++------
drivers/gpu/drm/i915/intel_gvt.c | 13 ++++---
drivers/gpu/drm/i915/intel_memory_region.c | 4 ++-
5 files changed, 64 insertions(+), 43 deletions(-)
--
2.24.1
next reply other threads:[~2020-01-09 9:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 9:06 Wambui Karuga [this message]
2020-01-09 9:06 ` [PATCH 1/5] drm/i915: conversion to new logging macros in i915/i915_vgpu.c Wambui Karuga
2020-01-09 9:06 ` [PATCH 2/5] drm/i915: conversion to new logging macros in i915/intel_csr.c Wambui Karuga
2020-01-09 9:06 ` [PATCH 3/5] drm/i915: conversion to new logging macros in i915/intel_device_info.c Wambui Karuga
2020-01-09 9:06 ` [PATCH 4/5] drm/i915: convert to new logging macros in i915/intel_gvt.c Wambui Karuga
2020-01-09 9:06 ` [PATCH 5/5] drm/i915: convert to new logging macros in i915/intel_memory_region.c Wambui Karuga
2020-01-17 15:47 ` [PATCH 0/5] Use new logging macros in drm/i915 Jani Nikula
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=cover.1578560355.git.wambui.karugax@gmail.com \
--to=wambui.karugax@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=sean@poorly.run \
/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