From: Karolina Drobnik <karolina.drobnik@intel.com>
To: <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Apply waitboosting before fence wait (rev2)
Date: Mon, 11 Jul 2022 07:19:33 +0200 [thread overview]
Message-ID: <5a866783-5477-475c-e160-6efe9dd45378@intel.com> (raw)
In-Reply-To: <165729212273.4506.9607116977312554430@emeril.freedesktop.org>
On 08.07.2022 16:55, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: Apply waitboosting before fence wait (rev2)
> URL : https://patchwork.freedesktop.org/series/105925/
> State : warning
>
> == Summary ==
>
> Error: dim checkpatch failed
> e35c61e9e46c drm/i915/gem: Look for waitboosting across the whole object prior to individual waits
> 85a4558b5d11 drm/i915: Bump GT idling delay to 2 jiffies
> 0ec610488c77 drm/i915/gt: Only kick the signal worker if there's been an update
> -:23: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
> #23:
> References: 047a1b877ed4 ("dma-buf & drm/amdgpu: remove dma_resv workaround")
Tags shouldn't be wrapped
> -:23: ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 047a1b877ed4 ("dma-buf & drm/amdgpu: remove dma_resv workaround")'
> #23:
> References: 047a1b877ed4 ("dma-buf & drm/amdgpu: remove dma_resv workaround")
"References:" line doesn't need "commit" keyword, it's a false positive
> total: 1 errors, 1 warnings, 0 checks, 9 lines checked
>
>
next prev parent reply other threads:[~2022-07-11 5:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 14:20 [Intel-gfx] [PATCH v2 0/3] drm/i915: Apply waitboosting before fence wait Karolina Drobnik
2022-07-08 14:20 ` [Intel-gfx] [PATCH v2 1/3] drm/i915/gem: Look for waitboosting across the whole object prior to individual waits Karolina Drobnik
2022-07-08 14:41 ` Rodrigo Vivi
2022-07-08 14:20 ` [Intel-gfx] [PATCH v2 2/3] drm/i915: Bump GT idling delay to 2 jiffies Karolina Drobnik
2022-07-08 14:20 ` [Intel-gfx] [PATCH v2 3/3] drm/i915/gt: Only kick the signal worker if there's been an update Karolina Drobnik
2022-07-08 14:40 ` Rodrigo Vivi
2022-07-11 14:10 ` Rodrigo Vivi
2022-07-12 6:29 ` Karolina Drobnik
2022-07-12 21:55 ` Rodrigo Vivi
2022-07-12 9:46 ` Andi Shyti
2022-07-08 14:55 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Apply waitboosting before fence wait (rev2) Patchwork
2022-07-11 5:19 ` Karolina Drobnik [this message]
2022-07-08 15:15 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-07-09 2:00 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-07-11 5:20 ` Karolina Drobnik
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=5a866783-5477-475c-e160-6efe9dd45378@intel.com \
--to=karolina.drobnik@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