All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "John Harrison" <john.c.harrison@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for drm/i915/guc: Update w/a 14019159160 (rev2)
Date: Sat, 06 Apr 2024 00:33:56 -0000	[thread overview]
Message-ID: <171236363692.1239316.17520670053941920531@8e613ede5ea5> (raw)
In-Reply-To: <20240308020129.728799-1-John.C.Harrison@Intel.com>

== Series Details ==

Series: drm/i915/guc: Update w/a 14019159160 (rev2)
URL   : https://patchwork.freedesktop.org/series/130890/
State : warning

== Summary ==

Error: dim checkpatch failed
ff350c317bfe drm/i915/guc: Update w/a 14019159160
-:20: WARNING:LONG_LINE_COMMENT: line length of 108 exceeds 100 columns
#20: FILE: drivers/gpu/drm/i915/gt/uc/abi/guc_klvs_abi.h:108:
+	GUC_WORKAROUND_KLV_SERIALIZED_RA_MODE				= 0x9001,	/* Wa_14019159160 */

-:21: WARNING:LONG_LINE_COMMENT: line length of 108 exceeds 100 columns
#21: FILE: drivers/gpu/drm/i915/gt/uc/abi/guc_klvs_abi.h:109:
+	GUC_WORKAROUND_KLV_AVOID_GFX_CLEAR_WHILE_ACTIVE			= 0x9006,	/* Wa_14019159160 */

-:62: 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
#62: FILE: drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c:829:
+	GEM_BUG_ON(*remain < size);

total: 0 errors, 3 warnings, 0 checks, 62 lines checked



  parent reply	other threads:[~2024-04-06  0:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08  2:01 [PATCH] drm/i915/guc: Update w/a 14019159160 John.C.Harrison
2024-03-08  2:42 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2024-03-08  2:42 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-03-08  3:04 ` ✓ Fi.CI.BAT: success " Patchwork
2024-03-08 14:36 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-03-12 16:24 ` [PATCH] " Matt Roper
2024-03-12 23:43   ` John Harrison
2024-03-12 23:50     ` Lucas De Marchi
2024-03-14 21:19     ` Matt Roper
2024-04-06  0:33 ` Patchwork [this message]
2024-04-06  0:33 ` ✗ Fi.CI.SPARSE: warning for drm/i915/guc: Update w/a 14019159160 (rev2) Patchwork
2024-04-06  0:47 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-04-06  9:32 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/guc: Update w/a 14019159160 (rev3) Patchwork
2024-04-06  9:32 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-04-06  9:50 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-04-08 21:04 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915/guc: Update w/a 14019159160 (rev4) Patchwork
2024-04-08 21:04 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-04-08 21:11 ` ✓ Fi.CI.BAT: success " Patchwork
2024-04-10  3:16 ` ✗ Fi.CI.IGT: failure " Patchwork

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=171236363692.1239316.17520670053941920531@8e613ede5ea5 \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=john.c.harrison@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.