public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for series starting with [CI,1/9] drm/i915: rename raw reg access functions
Date: Tue, 26 Mar 2019 21:13:13 -0000	[thread overview]
Message-ID: <20190326211313.29940.33969@emeril.freedesktop.org> (raw)
In-Reply-To: <20190326202146.27934-1-chris@chris-wilson.co.uk>

== Series Details ==

Series: series starting with [CI,1/9] drm/i915: rename raw reg access functions
URL   : https://patchwork.freedesktop.org/series/58604/
State : warning

== Summary ==

$ dim checkpatch origin/drm-tip
518022b1d8c7 drm/i915: rename raw reg access functions
-:302: CHECK:LINE_SPACING: Please use a blank line after function/struct/union/enum declarations
#302: FILE: drivers/gpu/drm/i915/intel_uncore.h:232:
+}
+__raw_read(8, b)

total: 0 errors, 0 warnings, 1 checks, 264 lines checked
9cb0c26b3438 drm/i915: add HAS_FORCEWAKE flag to uncore
578537728540 drm/i915: add uncore flags for unclaimed mmio
db6d1bf4fef7 drm/i915: take a ref to the rpm in the uncore structure
3165d80fee26 drm/i915: switch uncore mmio funcs to use intel_uncore
-:46: WARNING:LONG_LINE: line over 100 characters
#46: FILE: drivers/gpu/drm/i915/i915_drv.h:3488:
+#define I915_WRITE16_NOTRACE(reg__, val__) __I915_REG_OP(write16_notrace, dev_priv, (reg__), (val__))

-:231: ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#231: FILE: drivers/gpu/drm/i915/intel_uncore.h:278:
+#define __uncore_read(name__, x__, s__, trace__) \
+static inline u##x__ intel_uncore_##name__(struct intel_uncore *uncore, \
+					   i915_reg_t reg) \
+{ \
+	return uncore->funcs.mmio_read##s__(uncore, reg, (trace__)); \
+}

-:277: WARNING:LINE_SPACING: Missing a blank line after declarations
#277: FILE: drivers/gpu/drm/i915/intel_uncore.h:324:
+	u32 upper, lower, old_upper, loop = 0;
+	upper = intel_uncore_read(uncore, upper_reg);

total: 1 errors, 2 warnings, 0 checks, 295 lines checked
02c209860d4d drm/i915: switch intel_uncore_forcewake_for_reg to intel_uncore
09af615477d2 drm/i915: intel_wait_for_register_fw to uncore
003222962ccd drm/i915: switch intel_wait_for_register to uncore
bc3211904f72 drm/i915: take a reference to uncore in the engine and use it
-:421: WARNING:LONG_LINE: line over 100 characters
#421: FILE: drivers/gpu/drm/i915/intel_engine_cs.c:1345:
+		   ENGINE_READ(engine, RING_CTL) & (RING_WAIT | RING_WAIT_SEMAPHORE) ? " [waiting]" : "");

-:1042: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'engine__' - possible side-effects?
#1042: FILE: drivers/gpu/drm/i915/intel_ringbuffer.h:48:
+#define __ENGINE_READ_OP(op__, engine__, reg__) \
+	__ENGINE_REG_OP(op__, (engine__), reg__((engine__)->mmio_base))

-:1054: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'engine__' - possible side-effects?
#1054: FILE: drivers/gpu/drm/i915/intel_ringbuffer.h:56:
+#define ENGINE_READ64(engine__, lower_reg__, upper_reg__) \
+	__ENGINE_REG_OP(read64_2x32, (engine__), \
+			lower_reg__((engine__)->mmio_base), \
+			upper_reg__((engine__)->mmio_base))

-:1061: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'engine__' - possible side-effects?
#1061: FILE: drivers/gpu/drm/i915/intel_ringbuffer.h:61:
+#define ENGINE_READ_IDX(engine__, reg__, idx__) \
+	__ENGINE_REG_OP(read, (engine__), reg__((engine__)->mmio_base, (idx__)))

-:1066: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'engine__' - possible side-effects?
#1066: FILE: drivers/gpu/drm/i915/intel_ringbuffer.h:64:
+#define __ENGINE_WRITE_OP(op__, engine__, reg__, val__) \
+	__ENGINE_REG_OP(op__, (engine__), reg__((engine__)->mmio_base), (val__))

total: 0 errors, 1 warnings, 4 checks, 967 lines checked

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

  parent reply	other threads:[~2019-03-26 21:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-26 20:21 [CI 1/9] drm/i915: rename raw reg access functions Chris Wilson
2019-03-26 20:21 ` [CI 2/9] drm/i915: add HAS_FORCEWAKE flag to uncore Chris Wilson
2019-03-26 20:21 ` [CI 3/9] drm/i915: add uncore flags for unclaimed mmio Chris Wilson
2019-03-26 20:21 ` [CI 4/9] drm/i915: take a ref to the rpm in the uncore structure Chris Wilson
2019-03-26 20:21 ` [CI 5/9] drm/i915: switch uncore mmio funcs to use intel_uncore Chris Wilson
2019-03-26 20:21 ` [CI 6/9] drm/i915: switch intel_uncore_forcewake_for_reg to intel_uncore Chris Wilson
2019-03-26 20:21 ` [CI 7/9] drm/i915: intel_wait_for_register_fw to uncore Chris Wilson
2019-03-26 20:21 ` [CI 8/9] drm/i915: switch intel_wait_for_register " Chris Wilson
2019-03-26 20:21 ` [CI 9/9] drm/i915: take a reference to uncore in the engine and use it Chris Wilson
2019-03-26 21:13 ` Patchwork [this message]
2019-03-26 21:18 ` ✗ Fi.CI.SPARSE: warning for series starting with [CI,1/9] drm/i915: rename raw reg access functions Patchwork
2019-03-26 21:44 ` ✓ Fi.CI.BAT: success " Patchwork
2019-03-27  7:58   ` Jani Nikula
2019-03-27  9:28 ` ✓ 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=20190326211313.29940.33969@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=chris@chris-wilson.co.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox