From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Andi Shyti" <andi.shyti@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Add drm_dbg_ratelimited() (rev2)
Date: Thu, 07 Dec 2023 01:44:45 -0000 [thread overview]
Message-ID: <170191348503.28719.16675154275858361489@emeril.freedesktop.org> (raw)
In-Reply-To: <20231206210948.106238-1-andi.shyti@linux.intel.com>
== Series Details ==
Series: Add drm_dbg_ratelimited() (rev2)
URL : https://patchwork.freedesktop.org/series/124894/
State : warning
== Summary ==
Error: dim checkpatch failed
771479080ffb drm/print: Add drm_dbg_ratelimited
c3c299917b16 drm/i915: Ratelimit debug log in vm_fault_ttm
-:9: WARNING:COMMIT_LOG_USE_LINK: Unknown link reference 'References:', use 'Link:' or 'Closes:' instead
#9:
References: https://gitlab.freedesktop.org/drm/intel/-/issues/7038
total: 0 errors, 1 warnings, 0 checks, 11 lines checked
next prev parent reply other threads:[~2023-12-07 1:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 21:09 [Intel-gfx] [PATCH RESEND AGAIN v2 0/2] Add drm_dbg_ratelimited() Andi Shyti
2023-12-06 21:09 ` [Intel-gfx] [PATCH RESEND AGAIN v2 1/2] drm/print: Add drm_dbg_ratelimited Andi Shyti
2023-12-06 21:09 ` [Intel-gfx] [PATCH RESEND AGAIN v2 2/2] drm/i915: Ratelimit debug log in vm_fault_ttm Andi Shyti
2023-12-07 1:44 ` Patchwork [this message]
2023-12-07 1:44 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Add drm_dbg_ratelimited() (rev2) Patchwork
2023-12-07 1:56 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-12-07 3:19 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-12-07 9:00 ` [Intel-gfx] [PATCH RESEND AGAIN v2 0/2] Add drm_dbg_ratelimited() Thomas Zimmermann
2023-12-07 9:10 ` Maxime Ripard
2023-12-07 9:23 ` Andi Shyti
2023-12-07 13:06 ` Maxime Ripard
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=170191348503.28719.16675154275858361489@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=andi.shyti@linux.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 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).