All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [PATCH 0/3] drm/i915: remove __i915_printk()
Date: Tue,  6 Aug 2024 16:38:29 +0300	[thread overview]
Message-ID: <cover.1722951405.git.jani.nikula@intel.com> (raw)

I don't think we need the bug reporting request in the few specific
places that lead to __i915_printk(). With them gone, there's really no
need for __i915_printk(). Just switch to regular drm logging.

Jani Nikula (3):
  drm/i915: remove a few __i915_printk() uses
  drm/i915: remove i915_report_error()
  drm/i915: remove __i915_printk()

 drivers/gpu/drm/i915/i915_driver.c |  8 ++---
 drivers/gpu/drm/i915/i915_utils.c  | 51 +++---------------------------
 drivers/gpu/drm/i915/i915_utils.h  | 16 ++++------
 3 files changed, 15 insertions(+), 60 deletions(-)

-- 
2.39.2


             reply	other threads:[~2024-08-06 13:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-06 13:38 Jani Nikula [this message]
2024-08-06 13:38 ` [PATCH 1/3] drm/i915: remove a few __i915_printk() uses Jani Nikula
2024-08-06 19:32   ` Cavitt, Jonathan
2024-08-07 10:27   ` Tvrtko Ursulin
2024-08-07 11:21     ` Jani Nikula
2024-08-07 14:41   ` Andi Shyti
2024-08-06 13:38 ` [PATCH 2/3] drm/i915: remove i915_report_error() Jani Nikula
2024-08-06 19:38   ` Cavitt, Jonathan
2024-08-07 10:33   ` Tvrtko Ursulin
2024-08-07 14:44   ` Andi Shyti
2024-08-06 13:38 ` [PATCH 3/3] drm/i915: remove __i915_printk() Jani Nikula
2024-08-06 19:41   ` Cavitt, Jonathan
2024-08-07 10:45   ` Tvrtko Ursulin
2024-08-07 11:40     ` Jani Nikula
2024-08-07 14:25       ` Tvrtko Ursulin
2024-08-07 14:45   ` Andi Shyti
2024-08-06 15:29 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-08-06 15:30 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2024-08-06 15:30 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-08-07  5:48 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-08-08 14:45 ` [PATCH 0/3] " 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.1722951405.git.jani.nikula@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.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 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.