Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@linux.intel.com>
To: intel-gfx <intel-gfx@lists.freedesktop.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Cc: Andrzej Hajda <andrzej.hajda@intel.com>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Sam Ravnborg <sam@ravnborg.org>,
	Maxime Ripard <mripard@kernel.org>,
	Matthew Auld <matthew.auld@intel.com>,
	Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@gmail.com>,
	Nirmoy Das <nirmoy.das@intel.com>
Subject: [Intel-gfx] [PATCH RESEND v2 0/2] Add drm_dbg_ratelimited()
Date: Tue, 10 Oct 2023 14:15:43 +0200	[thread overview]
Message-ID: <20231010121545.1046793-1-andi.shyti@linux.intel.com> (raw)

Hi,

I might have picked up the wrong series and missed some reviews
and the extra patch from Nirmoy with a real use of the
drm_dbg_ratelimited() that John was looking for.

Thanks,
Andi

v2:
pick the right patch with the following changes:
 - add more r-b's
 - add a patch 2 where the drm_dbg_ratelimited is actually used.

Nirmoy Das (2):
  drm/print: Add drm_dbg_ratelimited
  drm/i915: Ratelimit debug log in vm_fault_ttm

 drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 5 +++--
 include/drm/drm_print.h                 | 3 +++
 2 files changed, 6 insertions(+), 2 deletions(-)

-- 
2.40.1


             reply	other threads:[~2023-10-10 12:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-10 12:15 Andi Shyti [this message]
2023-10-10 12:15 ` [Intel-gfx] [PATCH RESEND v2 1/2] drm/print: Add drm_dbg_ratelimited Andi Shyti
2023-10-10 20:39   ` Hamza Mahfooz
2023-10-10 12:15 ` [Intel-gfx] [PATCH RESEND v2 2/2] drm/i915: Ratelimit debug log in vm_fault_ttm Andi Shyti
2023-10-10 18:25 ` [Intel-gfx] [PATCH RESEND v2 0/2] Add drm_dbg_ratelimited() John Harrison
2023-10-10 20:31   ` Andi Shyti
2023-10-10 22:57 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2023-10-10 22:57 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-10-10 23:10 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-10-11 11:46 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-10-24 17:20 ` [Intel-gfx] [PATCH RESEND v2 0/2] " Andi Shyti

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=20231010121545.1046793-1-andi.shyti@linux.intel.com \
    --to=andi.shyti@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=andrzej.hajda@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.auld@intel.com \
    --cc=mripard@kernel.org \
    --cc=nirmoy.das@intel.com \
    --cc=sam@ravnborg.org \
    --cc=tzimmermann@suse.de \
    /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