intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Jim Cromie" <jim.cromie@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm: use dyndbg in drm_print (rev3)
Date: Sat, 31 Jul 2021 21:52:41 -0000	[thread overview]
Message-ID: <162776836140.3955.17284049668375127785@emeril.freedesktop.org> (raw)
In-Reply-To: <20210731214211.657280-1-jim.cromie@gmail.com>

== Series Details ==

Series: drm: use dyndbg in drm_print (rev3)
URL   : https://patchwork.freedesktop.org/series/92542/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
ab95444b671f moduleparam: add data member to struct kernel_param
7193036bdfae dyndbg: add dyndbg-bitmap definer and callbacks
-:89: WARNING:TRAILING_SEMICOLON: macros should not use a trailing semicolon
#89: FILE: include/linux/dynamic_debug.h:260:
+#define DEFINE_DYNDBG_BITMAP(name, value, bitmap_desc, ...)	\
+	struct dyndbg_bitdesc dyndbg_classes_##name[] =		\
+	{ __VA_ARGS__, { NULL, NULL } };			\
+	module_param_cbd(name, &param_ops_dyndbg, value, 0644,	\
+			 &dyndbg_classes_##name);

-:117: CHECK:SPACING: No space is necessary after a cast
#117: FILE: lib/dynamic_debug.c:1168:
+	struct dyndbg_bitdesc *bitmap = (struct dyndbg_bitdesc *) kp->data;

-:131: ERROR:TRAILING_STATEMENTS: trailing statements should be on next line
#131: FILE: lib/dynamic_debug.c:1182:
+	for (bitsmax = 0; bitmap[bitsmax].prefix; bitsmax++);

-:134: CHECK:BRACES: Blank lines aren't necessary after an open brace '{'
#134: FILE: lib/dynamic_debug.c:1185:
+	for_each_set_bit(bitpos, &changes, min(--bitsmax, 64)) {
+

total: 1 errors, 1 warnings, 2 checks, 106 lines checked
f73667a8cacb i915/gvt: remove spaces in pr_debug "gvt: core:" etc prefixes
-:43: CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#43: FILE: drivers/gpu/drm/i915/gvt/debug.h:39:
+	pr_debug("gvt:core: "fmt, ##args)

-:47: CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#47: FILE: drivers/gpu/drm/i915/gvt/debug.h:42:
+	pr_debug("gvt:irq: "fmt, ##args)

-:51: CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#51: FILE: drivers/gpu/drm/i915/gvt/debug.h:45:
+	pr_debug("gvt:mm: "fmt, ##args)

-:55: CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#55: FILE: drivers/gpu/drm/i915/gvt/debug.h:48:
+	pr_debug("gvt:mmio: "fmt, ##args)

-:59: CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#59: FILE: drivers/gpu/drm/i915/gvt/debug.h:51:
+	pr_debug("gvt:dpy: "fmt, ##args)

-:63: CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#63: FILE: drivers/gpu/drm/i915/gvt/debug.h:54:
+	pr_debug("gvt:el: "fmt, ##args)

-:67: CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#67: FILE: drivers/gpu/drm/i915/gvt/debug.h:57:
+	pr_debug("gvt:sched: "fmt, ##args)

-:71: CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#71: FILE: drivers/gpu/drm/i915/gvt/debug.h:60:
+	pr_debug("gvt:render: "fmt, ##args)

-:75: CHECK:CONCATENATED_STRING: Concatenated strings should use spaces between elements
#75: FILE: drivers/gpu/drm/i915/gvt/debug.h:63:
+	pr_debug("gvt:cmd: "fmt, ##args)

total: 0 errors, 0 warnings, 9 checks, 39 lines checked
816d1412b3f8 i915/gvt: control pr_debug("gvt:")s with bits in parameters/debug_gvt
-:57: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'key' - possible side-effects?
#57: FILE: drivers/gpu/drm/i915/i915_params.c:273:
+#define _help(key)	"\t\"" key "\"\t: help for " key "\n"

-:58: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'key' - possible side-effects?
#58: FILE: drivers/gpu/drm/i915/i915_params.c:274:
+#define cmd_help(key)	{ .prefix = key, .help = key ": help for " key }

-:76: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#76: FILE: drivers/gpu/drm/i915/i915_params.c:292:
+DEFINE_DYNDBG_BITMAP(debug_gvt, &__gvt_debug,
+		   I915_DYNDBG_PARM_DESC(debug_gvt),

total: 0 errors, 0 warnings, 3 checks, 53 lines checked
7b12f8b286e8 drm/print: add choice to use dynamic debug in drm-debug
-:93: WARNING:TYPO_SPELLING: 'doesnt' may be misspelled - perhaps 'doesn't'?
#93: 
 - "1","2","3" are allowed, 1-9 is effective max. 2 doesnt imply 1.
                                                    ^^^^^^

-:344: CHECK:LINE_SPACING: Please don't use multiple blank lines
#344: FILE: include/drm/drm_print.h:548:
 
+

total: 0 errors, 1 warnings, 1 checks, 226 lines checked
04b4dd37cb1c amdgpu: define a dydbg-bitmap to control categorized pr_debugs
-:30: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'key' - possible side-effects?
#30: FILE: drivers/gpu/drm/amd/display/dc/core/dc_debug.c:43:
+#define _help(key)	"\t\t" key " : help for " key "\n"

-:31: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'key' - possible side-effects?
#31: FILE: drivers/gpu/drm/amd/display/dc/core/dc_debug.c:44:
+#define cmd_help(key)	{ .prefix = key, .help = "help for " key }

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



  parent reply	other threads:[~2021-07-31 21:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-31 21:41 [Intel-gfx] [PATCH v4 0/7] drm: use dyndbg in drm_print Jim Cromie
2021-07-31 21:41 ` [Intel-gfx] [PATCH v4 1/7] drm/print: fixup spelling in a comment Jim Cromie
2021-07-31 21:41 ` [Intel-gfx] [PATCH v4 2/7] moduleparam: add data member to struct kernel_param Jim Cromie
2021-08-02 16:18   ` Emil Velikov
2021-08-02 18:36     ` jim.cromie
2021-07-31 21:42 ` [Intel-gfx] [PATCH v4 3/7] dyndbg: add dyndbg-bitmap definer and callbacks Jim Cromie
2021-08-02 16:24   ` Emil Velikov
2021-08-02 18:40     ` jim.cromie
2021-07-31 21:42 ` [Intel-gfx] [PATCH v4 4/7] i915/gvt: remove spaces in pr_debug "gvt: core:" etc prefixes Jim Cromie
2021-07-31 21:42 ` [Intel-gfx] [PATCH v4 5/7] i915/gvt: control pr_debug("gvt:")s with bits in parameters/debug_gvt Jim Cromie
2021-08-02 16:27   ` Emil Velikov
2021-07-31 21:42 ` [Intel-gfx] [PATCH v4 6/7] drm/print: add choice to use dynamic debug in drm-debug Jim Cromie
2021-07-31 21:42 ` [Intel-gfx] [PATCH v4 7/7] amdgpu: define a dydbg-bitmap to control categorized pr_debugs Jim Cromie
2021-07-31 21:52 ` Patchwork [this message]
2021-07-31 21:56 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm: use dyndbg in drm_print (rev3) Patchwork
2021-07-31 22:20 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-08-01  0:54 ` [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=162776836140.3955.17284049668375127785@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jim.cromie@gmail.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;
as well as URLs for NNTP newsgroup(s).