From: John Harrison <john.c.harrison@intel.com>
To: <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Improvements to GuC load failure handling (rev3)
Date: Thu, 23 Mar 2023 15:30:19 -0700 [thread overview]
Message-ID: <ce6360f2-07d9-a2bc-d1fc-141981af05ea@intel.com> (raw)
In-Reply-To: <167953924945.6628.8427877386808361140@emeril.freedesktop.org>
On 3/22/2023 19:40, Patchwork wrote:
> == Series Details ==
>
> Series: Improvements to GuC load failure handling (rev3)
> URL : https://patchwork.freedesktop.org/series/114168/
> State : warning
>
> == Summary ==
>
> Error: dim checkpatch failed
> b4df7f16c846 drm/i915/guc: Improve GuC load error reporting
> 2be0fcf3087c drm/i915/guc: Allow for very slow GuC loading
> -:21: WARNING:COMMIT_LOG_USE_LINK: Unknown link reference 'References:', use 'Link:' instead
> #21:
> References: https://gitlab.freedesktop.org/drm/intel/-/issues/7931
>
> -:22: WARNING:COMMIT_LOG_USE_LINK: Unknown link reference 'References:', use 'Link:' instead
> #22:
> References: https://gitlab.freedesktop.org/drm/intel/-/issues/8060
>
> -:23: WARNING:COMMIT_LOG_USE_LINK: Unknown link reference 'References:', use 'Link:' instead
> #23:
> References: https://gitlab.freedesktop.org/drm/intel/-/issues/8083
>
> -:24: WARNING:COMMIT_LOG_USE_LINK: Unknown link reference 'References:', use 'Link:' instead
> #24:
> References: https://gitlab.freedesktop.org/drm/intel/-/issues/8136
>
> -:25: WARNING:COMMIT_LOG_USE_LINK: Unknown link reference 'References:', use 'Link:' instead
These issues appear to be the tool getting confused about bug references
versus patchwork links. Other patches in the tree use the references tag
for bug links.
John.
> #25:
> References: https://gitlab.freedesktop.org/drm/intel/-/issues/8137
>
> total: 0 errors, 5 warnings, 0 checks, 85 lines checked
>
>
next prev parent reply other threads:[~2023-03-23 22:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 22:06 [Intel-gfx] [PATCH v2 0/2] Improvements to GuC load failure handling John.C.Harrison
2023-03-16 22:06 ` [Intel-gfx] [PATCH v2 1/2] drm/i915/guc: Improve GuC load error reporting John.C.Harrison
2023-03-16 22:06 ` [Intel-gfx] [PATCH v2 2/2] drm/i915/guc: Allow for very slow GuC loading John.C.Harrison
2023-03-17 22:33 ` Dixit, Ashutosh
2023-03-22 21:14 ` Ceraolo Spurio, Daniele
2023-03-23 2:40 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Improvements to GuC load failure handling (rev3) Patchwork
2023-03-23 22:30 ` John Harrison [this message]
2023-03-23 2:40 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-03-23 2:52 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2023-03-23 22:29 ` John Harrison
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=ce6360f2-07d9-a2bc-d1fc-141981af05ea@intel.com \
--to=john.c.harrison@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