linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aurabindo Pillai <mail@aurabindo.in>
To: christian.koenig@amd.com, alexander.deucher@amd.com, David1.Zhou@amd.com
Cc: airlied@linux.ie, daniel@ffwll.ch, Felix.Kuehling@amd.com,
	amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] drm/amd/amdgpu: Add print format prefix
Date: Wed,  8 Apr 2020 21:28:12 -0400	[thread overview]
Message-ID: <20200409012815.22309-1-mail@aurabindo.in> (raw)

Changes in v2

* Add dev_fmt format prefix
* Removed hardcoded module names in pr_* and dev_* prints

Aurabindo Pillai (3):
  drm/amd/amdgpu: add prefix for pr_* prints
  drm/amd/amdgpu: add print prefix for dev_* variants
  drm/amd/amdgpu: remove hardcoded module name in prints

 drivers/gpu/drm/amd/amdgpu/amdgpu.h              | 12 ++++++++++++
 drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c |  6 +++---
 drivers/gpu/drm/amd/amdgpu/amdgpu_device.c       |  4 ++--
 drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c          |  2 +-
 drivers/gpu/drm/amd/amdgpu/gmc_v6_0.c            |  2 +-
 drivers/gpu/drm/amd/amdgpu/gmc_v7_0.c            |  2 +-
 drivers/gpu/drm/amd/amdgpu/gmc_v8_0.c            |  2 +-
 7 files changed, 21 insertions(+), 9 deletions(-)

-- 
2.26.0


             reply	other threads:[~2020-04-09  1:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-09  1:28 Aurabindo Pillai [this message]
2020-04-09  1:28 ` [PATCH v2 1/3] drm/amd/amdgpu: add prefix for pr_* prints Aurabindo Pillai
2020-04-09  1:28 ` [PATCH v2 2/3] drm/amd/amdgpu: add print prefix for dev_* variants Aurabindo Pillai
2020-04-09  1:28 ` [PATCH v2 3/3] drm/amd/amdgpu: remove hardcoded module name in prints Aurabindo Pillai
2020-04-13 15:12 ` [PATCH v2 0/3] drm/amd/amdgpu: Add print format prefix Alex Deucher

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=20200409012815.22309-1-mail@aurabindo.in \
    --to=mail@aurabindo.in \
    --cc=David1.Zhou@amd.com \
    --cc=Felix.Kuehling@amd.com \
    --cc=airlied@linux.ie \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).