All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Matthew Auld" <matthew.auld@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v2,1/9] drm/doc/rfc: i915 DG1 uAPI
Date: Thu, 29 Apr 2021 16:21:03 -0000	[thread overview]
Message-ID: <161971326393.20425.10657635929196629264@emeril.freedesktop.org> (raw)
In-Reply-To: <20210429103056.407067-1-matthew.auld@intel.com>

== Series Details ==

Series: series starting with [v2,1/9] drm/doc/rfc: i915 DG1 uAPI
URL   : https://patchwork.freedesktop.org/series/89648/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
04da5ac951fc drm/doc/rfc: i915 DG1 uAPI
-:63: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#63: 
new file mode 100644

-:68: WARNING:SPDX_LICENSE_TAG: Missing or malformed SPDX-License-Identifier tag in line 1
#68: FILE: Documentation/gpu/rfc/i915_gem_lmem.h:1:
+/**

-:141: ERROR:CODE_INDENT: code indent should use tabs where possible
#141: FILE: Documentation/gpu/rfc/i915_gem_lmem.h:74:
+        __u64 rsvd1[8];$

-:141: WARNING:LEADING_SPACE: please, no spaces at the start of a line
#141: FILE: Documentation/gpu/rfc/i915_gem_lmem.h:74:
+        __u64 rsvd1[8];$

-:195: ERROR:CODE_INDENT: code indent should use tabs where possible
#195: FILE: Documentation/gpu/rfc/i915_gem_lmem.h:128:
+        __u32 rsvd[3];$

-:195: WARNING:LEADING_SPACE: please, no spaces at the start of a line
#195: FILE: Documentation/gpu/rfc/i915_gem_lmem.h:128:
+        __u32 rsvd[3];$

-:202: WARNING:LONG_LINE: line length of 124 exceeds 100 columns
#202: FILE: Documentation/gpu/rfc/i915_gem_lmem.h:135:
+#define DRM_IOCTL_I915_GEM_CREATE_EXT	DRM_IOWR(DRM_COMMAND_BASE + DRM_I915_GEM_CREATE_EXT, struct drm_i915_gem_create_ext)

-:311: WARNING:SPDX_LICENSE_TAG: Missing or malformed SPDX-License-Identifier tag in line 1
#311: FILE: Documentation/gpu/rfc/i915_gem_lmem.rst:1:
+=========================

total: 2 errors, 6 warnings, 0 checks, 375 lines checked
cde9b3fe065c drm/i915: mark stolen as private
45d5ce64820c drm/i915/query: Expose memory regions through the query uAPI
-:224: ERROR:CODE_INDENT: code indent should use tabs where possible
#224: FILE: include/uapi/drm/i915_drm.h:2541:
+        __u64 rsvd1[8];$

-:224: WARNING:LEADING_SPACE: please, no spaces at the start of a line
#224: FILE: include/uapi/drm/i915_drm.h:2541:
+        __u64 rsvd1[8];$

-:278: ERROR:CODE_INDENT: code indent should use tabs where possible
#278: FILE: include/uapi/drm/i915_drm.h:2595:
+        __u32 rsvd[3];$

-:278: WARNING:LEADING_SPACE: please, no spaces at the start of a line
#278: FILE: include/uapi/drm/i915_drm.h:2595:
+        __u32 rsvd[3];$

total: 2 errors, 2 warnings, 0 checks, 237 lines checked
b333347afffc drm/i915: rework gem_create flow for upcoming extensions
ee534b2bfe4d drm/i915/uapi: introduce drm_i915_gem_create_ext
-:151: WARNING:LONG_LINE: line length of 124 exceeds 100 columns
#151: FILE: include/uapi/drm/i915_drm.h:442:
+#define DRM_IOCTL_I915_GEM_CREATE_EXT	DRM_IOWR(DRM_COMMAND_BASE + DRM_I915_GEM_CREATE_EXT, struct drm_i915_gem_create_ext)

total: 0 errors, 1 warnings, 0 checks, 140 lines checked
d3c82d03ea86 drm/i915/uapi: implement object placement extension
548511f53787 drm/i915/lmem: support optional CPU clearing for special internal use
-:78: WARNING:MEMORY_BARRIER: memory barrier without comment
#78: FILE: drivers/gpu/drm/i915/gem/i915_gem_region.c:117:
+		wmb();

-:114: WARNING:LINE_SPACING: Missing a blank line after declarations
#114: FILE: drivers/gpu/drm/i915/selftests/intel_memory_region.c:637:
+	struct drm_i915_private *i915 = arg;
+	I915_RND_STATE(prng);

total: 0 errors, 2 warnings, 0 checks, 156 lines checked
da6d86664790 drm/i915/gem: clear userspace buffers for LMEM
bf2f129104e6 drm/i915/gem: hide new uAPI behind CONFIG_BROKEN


_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2021-04-29 16:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29 10:30 [PATCH v2 1/9] drm/doc/rfc: i915 DG1 uAPI Matthew Auld
2021-04-29 10:30 ` [Intel-gfx] " Matthew Auld
2021-04-29 10:30 ` [PATCH v2 2/9] drm/i915: mark stolen as private Matthew Auld
2021-04-29 10:30   ` [Intel-gfx] " Matthew Auld
2021-04-29 10:30 ` [PATCH v2 3/9] drm/i915/query: Expose memory regions through the query uAPI Matthew Auld
2021-04-29 10:30   ` [Intel-gfx] " Matthew Auld
2021-04-29 10:30 ` [PATCH v2 4/9] drm/i915: rework gem_create flow for upcoming extensions Matthew Auld
2021-04-29 10:30   ` [Intel-gfx] " Matthew Auld
2021-04-29 10:30 ` [PATCH v2 5/9] drm/i915/uapi: introduce drm_i915_gem_create_ext Matthew Auld
2021-04-29 10:30   ` [Intel-gfx] " Matthew Auld
2021-04-29 10:30 ` [PATCH v2 6/9] drm/i915/uapi: implement object placement extension Matthew Auld
2021-04-29 10:30   ` [Intel-gfx] " Matthew Auld
2021-04-29 10:30 ` [PATCH v2 7/9] drm/i915/lmem: support optional CPU clearing for special internal use Matthew Auld
2021-04-29 10:30   ` [Intel-gfx] " Matthew Auld
2021-04-29 10:30 ` [PATCH v2 8/9] drm/i915/gem: clear userspace buffers for LMEM Matthew Auld
2021-04-29 10:30   ` [Intel-gfx] " Matthew Auld
2021-04-29 10:30 ` [PATCH v2 9/9] drm/i915/gem: hide new uAPI behind CONFIG_BROKEN Matthew Auld
2021-04-29 10:30   ` [Intel-gfx] " Matthew Auld
2021-04-29 16:21 ` Patchwork [this message]
2021-04-29 16:22 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [v2,1/9] drm/doc/rfc: i915 DG1 uAPI Patchwork
2021-04-29 16:51 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-04-29 19:32 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=161971326393.20425.10657635929196629264@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.auld@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.