All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: ravitejax.goud.talla@intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/gen11: Moving WAs to icl_gt_workarounds_init()
Date: Tue, 23 Nov 2021 15:09:05 -0000	[thread overview]
Message-ID: <163768014507.2115.9022081803020572380@emeril.freedesktop.org> (raw)
In-Reply-To: <20211123144559.3474989-1-ravitejax.goud.talla@intel.com>

== Series Details ==

Series: drm/i915/gen11: Moving WAs to icl_gt_workarounds_init()
URL   : https://patchwork.freedesktop.org/series/97208/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
8a0b3247925b drm/i915/gen11: Moving WAs to icl_gt_workarounds_init()
-:23: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#23: FILE: drivers/gpu/drm/i915/gt/intel_workarounds.c:1236:
+	wa_write_or(wal, UNSLICE_UNIT_LEVEL_CLKGATE2,
+			PSDUNIT_CLKGATE_DIS);

-:27: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#27: FILE: drivers/gpu/drm/i915/gt/intel_workarounds.c:1240:
+	wa_write_or(wal,
+			SUBSLICE_UNIT_LEVEL_CLKGATE,

total: 0 errors, 0 warnings, 2 checks, 30 lines checked



  reply	other threads:[~2021-11-23 15:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-23 14:45 [Intel-gfx] [PATCH] drm/i915/gen11: Moving WAs to icl_gt_workarounds_init() ravitejax.goud.talla
2021-11-23 15:09 ` Patchwork [this message]
2021-11-23 15:44 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2021-11-23 17:06 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-11-26 16:33 ` [Intel-gfx] [PATCH] " Talla, RavitejaX Goud
2021-11-26 18:16 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915/gen11: Moving WAs to icl_gt_workarounds_init() (rev2) Patchwork
2021-12-01  3:07 ` [Intel-gfx] [PATCH] drm/i915/gen11: Moving WAs to icl_gt_workarounds_init() 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=163768014507.2115.9022081803020572380@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ravitejax.goud.talla@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.