From: "Gupta, Anshuman" <anshuman.gupta@intel.com>
To: <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/dgfx: Grab wakeref at i915_ttm_unmap_virtual (rev4)
Date: Mon, 31 Oct 2022 18:11:28 +0530 [thread overview]
Message-ID: <ad4ba092-f560-1fe1-45e9-feae928f8cb2@intel.com> (raw)
In-Reply-To: <166687564581.4254.1906121029427505665@emeril.freedesktop.org>
On 10/27/2022 6:30 PM, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/dgfx: Grab wakeref at i915_ttm_unmap_virtual (rev4)
> URL : https://patchwork.freedesktop.org/series/108972/
> State : warning
>
> == Summary ==
>
> Error: dim checkpatch failed
> d83d4490c920 drm/i915: Encapsulate lmem rpm stuff in intel_runtime_pm
> -:69: WARNING:LONG_LINE: line length of 104 exceeds 100 columns
> #69: FILE: drivers/gpu/drm/i915/gem/i915_gem_ttm.c:1105:
> + list_add(&obj->userfault_link, &to_i915(obj->base.dev)->runtime_pm.lmem_userfault_list);
Code if block is more readable in single line.
>
> total: 0 errors, 1 warnings, 0 checks, 147 lines checked
> 721d116886f7 drm/i915/dgfx: Grab wakeref at i915_ttm_unmap_virtual
> -:44: WARNING:AVOID_BUG: Do not crash the kernel unless it is absolutely unavoidable--use WARN_ON_ONCE() plus recovery code (if feasible) instead of BUG() or variants
> #44: FILE: drivers/gpu/drm/i915/gem/i915_gem_mman.c:564:
> + GEM_BUG_ON(!obj->userfault_count);
>
> -:155: CHECK:UNCOMMENTED_DEFINITION: spinlock_t definition without comment
Above is a false alarm, there is already an existing comment about the
lock usages.
Br,
Anshuman Gupta.
> #155: FILE: drivers/gpu/drm/i915/intel_runtime_pm.h:67:
> + spinlock_t lmem_userfault_lock;
>
> total: 0 errors, 1 warnings, 1 checks, 109 lines checked
>
>
next prev parent reply other threads:[~2022-10-31 12:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 9:22 [Intel-gfx] [PATCH v3 0/2] drm/i915/dgfx: Grab wakeref at i915_ttm_unmap_virtual Anshuman Gupta
2022-10-27 9:22 ` [Intel-gfx] [PATCH v3 1/2] drm/i915: Encapsulate lmem rpm stuff in intel_runtime_pm Anshuman Gupta
2022-10-27 9:22 ` [Intel-gfx] [PATCH v3 2/2] drm/i915/dgfx: Grab wakeref at i915_ttm_unmap_virtual Anshuman Gupta
2022-10-27 13:00 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/dgfx: Grab wakeref at i915_ttm_unmap_virtual (rev4) Patchwork
2022-10-31 12:41 ` Gupta, Anshuman [this message]
2022-10-27 13:00 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-10-27 14:40 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-10-29 5:59 ` Gupta, Anshuman
2022-10-31 6:44 ` Vudum, Lakshminarayana
2022-10-31 6:07 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-10-31 8:39 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-10-31 12:25 ` Gupta, Anshuman
2022-10-31 13:05 ` Gupta, Anshuman
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=ad4ba092-f560-1fe1-45e9-feae928f8cb2@intel.com \
--to=anshuman.gupta@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