From: Patchwork <patchwork@emeril.freedesktop.org>
To: Ramalingam C <ramalingam.c@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for GMBUS changes (rev6)
Date: Thu, 28 Jun 2018 14:31:45 -0000 [thread overview]
Message-ID: <20180628143145.19700.36561@emeril.freedesktop.org> (raw)
In-Reply-To: <1530192889-5789-1-git-send-email-ramalingam.c@intel.com>
== Series Details ==
Series: GMBUS changes (rev6)
URL : https://patchwork.freedesktop.org/series/41632/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
3e6e90c178c0 drm/i915/gmbus: Increase the Bytes per Rd/Wr Op
7a76dec751ca drm/i915/gmbus: Enable burst read
-:42: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'dev_priv' - possible side-effects?
#42: FILE: drivers/gpu/drm/i915/i915_drv.h:2577:
+#define HAS_GMBUS_BURST_READ(dev_priv) (INTEL_GEN(dev_priv) >= 10 || \
+ IS_GEMINILAKE(dev_priv) || \
+ IS_KABYLAKE(dev_priv))
total: 0 errors, 0 warnings, 1 checks, 130 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-06-28 14:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 13:34 [PATCH v6 0/2] GMBUS changes Ramalingam C
2018-06-28 13:34 ` [PATCH v5 1/2] drm/i915/gmbus: Increase the Bytes per Rd/Wr Op Ramalingam C
2018-06-28 13:34 ` [PATCH v6 2/2] drm/i915/gmbus: Enable burst read Ramalingam C
2018-06-28 14:31 ` Patchwork [this message]
2018-06-28 14:33 ` ✗ Fi.CI.SPARSE: warning for GMBUS changes (rev6) Patchwork
2018-06-28 14:49 ` ✓ Fi.CI.BAT: success " Patchwork
2018-06-28 17:40 ` ✓ 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=20180628143145.19700.36561@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ramalingam.c@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;
as well as URLs for NNTP newsgroup(s).