From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Daniele Ceraolo Spurio" <daniele.ceraolospurio@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/wopcm: Handle pre-programmed WOPCM registers
Date: Fri, 14 Jan 2022 20:00:12 -0000 [thread overview]
Message-ID: <164219041292.15568.8587250148409336918@emeril.freedesktop.org> (raw)
In-Reply-To: <20220114193315.3271408-1-daniele.ceraolospurio@intel.com>
== Series Details ==
Series: drm/i915/wopcm: Handle pre-programmed WOPCM registers
URL : https://patchwork.freedesktop.org/series/98910/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
03db6d6cfb02 drm/i915/wopcm: Handle pre-programmed WOPCM registers
-:14: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#14:
sometimes using a smaller WOPCM size that the actual HW support (which isn't
-:36: CHECK:SPACING: spaces preferred around that '<<' (ctx:VxV)
#36: FILE: drivers/gpu/drm/i915/gt/uc/intel_guc_reg.h:98:
+#define GUC_IS_PRIVILEGED (1<<29)
^
total: 0 errors, 1 warnings, 1 checks, 134 lines checked
next prev parent reply other threads:[~2022-01-14 20:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 19:33 [PATCH] drm/i915/wopcm: Handle pre-programmed WOPCM registers Daniele Ceraolo Spurio
2022-01-14 19:33 ` [Intel-gfx] " Daniele Ceraolo Spurio
2022-01-14 20:00 ` Patchwork [this message]
2022-01-14 20:01 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2022-01-14 20:26 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-01-17 12:40 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-01-20 18:13 ` [PATCH] " Teres Alexis, Alan Previn
2022-01-20 18:13 ` [Intel-gfx] " Teres Alexis, Alan Previn
2022-01-20 18:48 ` Matthew Brost
2022-01-20 18:48 ` [Intel-gfx] " Matthew Brost
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=164219041292.15568.8587250148409336918@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=daniele.ceraolospurio@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 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.