All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Swathi Dhanavanthri" <swathi.dhanavanthri@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/dg2: Add workaround 22014600077 (rev2)
Date: Tue, 17 May 2022 22:23:12 -0000	[thread overview]
Message-ID: <165282619280.31031.7625044056445776615@emeril.freedesktop.org> (raw)
In-Reply-To: <20220517212905.24212-1-swathi.dhanavanthri@intel.com>

== Series Details ==

Series: drm/i915/dg2: Add workaround 22014600077 (rev2)
URL   : https://patchwork.freedesktop.org/series/104097/
State : warning

== Summary ==

Error: dim checkpatch failed
c6ced9357337 drm/i915/dg2: Add workaround 22014600077
-:7: WARNING:COMMIT_MESSAGE: Missing commit description - Add an appropriate one

-:34: WARNING:BLOCK_COMMENT_STYLE: Block comments use * on subsequent lines
#34: FILE: drivers/gpu/drm/i915/gt/intel_workarounds.c:2187:
+		       0 /* Wa_14012342262 :write-only reg, so skip
+			    verification */,

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



  reply	other threads:[~2022-05-17 22:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 21:29 [Intel-gfx] [PATCH v2] drm/i915/dg2: Add workaround 22014600077 Swathi Dhanavanthri
2022-05-17 22:23 ` Patchwork [this message]
2022-05-17 22:42 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dg2: Add workaround 22014600077 (rev2) Patchwork
2022-05-18  4:36 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-05-18 21:11   ` Dhanavanthri, Swathi
2022-05-18 22:21     ` Vudum, Lakshminarayana
2022-05-18 15:24 ` [Intel-gfx] [PATCH v2] drm/i915/dg2: Add workaround 22014600077 Matt Roper
2022-05-18 22:03 ` [Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/dg2: Add workaround 22014600077 (rev2) Patchwork
2022-05-19 16:54   ` Matt Roper

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=165282619280.31031.7625044056445776615@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=swathi.dhanavanthri@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.