From: Patchwork <patchwork@emeril.freedesktop.org>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Silence build error with UBSAN (rev2)
Date: Tue, 16 Oct 2018 10:33:09 -0000 [thread overview]
Message-ID: <20181016103309.2708.32171@emeril.freedesktop.org> (raw)
In-Reply-To: <20181015203410.155997-1-swboyd@chromium.org>
== Series Details ==
Series: drm/i915: Silence build error with UBSAN (rev2)
URL : https://patchwork.freedesktop.org/series/51025/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
8d9d30d99fd4 drm/i915: Silence build error with UBSAN
-:10: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#10:
> drivers/gpu/drm/i915/intel_engine_cs.o: In function `intel_engine_init_execlist':
-:44: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'n' - possible side-effects?
#44: FILE: drivers/gpu/drm/i915/intel_engine_cs.c:464:
+#define IS_POWER_OF_2(n) ((n) != 0 && ((n) & ((n) - 1)) == 0)
-:55: ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)
total: 1 errors, 1 warnings, 1 checks, 15 lines checked
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-10-16 10:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 20:34 [PATCH] drm/i915: Silence build error with UBSAN Stephen Boyd
2018-10-15 21:05 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-10-16 1:25 ` ✓ Fi.CI.IGT: " Patchwork
2018-10-16 9:59 ` [PATCH] " Jani Nikula
2018-10-16 10:07 ` Chris Wilson
2018-10-16 11:48 ` Jani Nikula
2018-10-16 10:33 ` Patchwork [this message]
2018-10-16 10:50 ` ✓ Fi.CI.BAT: success for drm/i915: Silence build error with UBSAN (rev2) Patchwork
2018-10-16 11:43 ` ✓ 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=20181016103309.2708.32171@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.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