From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Jouni Högander" <jouni.hogander@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Prepare intel_fb for Xe (rev10)
Date: Sun, 03 Dec 2023 12:21:07 -0000 [thread overview]
Message-ID: <170160606747.25281.2412370174601097419@emeril.freedesktop.org> (raw)
In-Reply-To: <20231203114840.841311-1-jouni.hogander@intel.com>
== Series Details ==
Series: Prepare intel_fb for Xe (rev10)
URL : https://patchwork.freedesktop.org/series/126507/
State : warning
== Summary ==
Error: dim checkpatch failed
9bcd0d54b877 drm/i915/display: use intel_bo_to_drm_bo in intel_fb.c
6f1114511f45 drm/i915/display: Convert intel_fb_modifier_to_tiling as non-static
fa768775a1c0 drm/i915/display: Handle invalid fb_modifier in intel_fb_modifier_to_tiling
38d5f12fa06c drm/i915/display: Split i915 specific code away from intel_fb.c
Traceback (most recent call last):
File "scripts/spdxcheck.py", line 6, in <module>
from ply import lex, yacc
ModuleNotFoundError: No module named 'ply'
-:173: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#173:
new file mode 100644
-:178: WARNING:SPDX_LICENSE_TAG: Improper SPDX comment style for 'drivers/gpu/drm/i915/display/intel_fb_bo.c', please use '//' instead
#178: FILE: drivers/gpu/drm/i915/display/intel_fb_bo.c:1:
+/* SPDX-License-Identifier: MIT */
-:178: WARNING:SPDX_LICENSE_TAG: Missing or malformed SPDX-License-Identifier tag in line 1
#178: FILE: drivers/gpu/drm/i915/display/intel_fb_bo.c:1:
+/* SPDX-License-Identifier: MIT */
total: 0 errors, 3 warnings, 0 checks, 239 lines checked
next prev parent reply other threads:[~2023-12-03 12:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 11:48 [Intel-gfx] [PATCH v9 0/4] Prepare intel_fb for Xe Jouni Högander
2023-12-03 11:48 ` [Intel-gfx] [PATCH v9 1/4] drm/i915/display: use intel_bo_to_drm_bo in intel_fb.c Jouni Högander
2023-12-03 11:48 ` [Intel-gfx] [PATCH v9 2/4] drm/i915/display: Convert intel_fb_modifier_to_tiling as non-static Jouni Högander
2023-12-03 11:48 ` [Intel-gfx] [PATCH v9 3/4] drm/i915/display: Handle invalid fb_modifier in intel_fb_modifier_to_tiling Jouni Högander
2023-12-03 11:48 ` [Intel-gfx] [PATCH v9 4/4] drm/i915/display: Split i915 specific code away from intel_fb.c Jouni Högander
2023-12-03 12:21 ` Patchwork [this message]
2023-12-03 12:21 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Prepare intel_fb for Xe (rev10) Patchwork
2023-12-03 12:33 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-12-03 14:04 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-12-04 5:23 ` Hogander, Jouni
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=170160606747.25281.2412370174601097419@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jouni.hogander@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox