From: Patchwork <patchwork@emeril.freedesktop.org>
To: "José Roberto de Souza" <jose.souza@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for drm/i915/aml: Add new Amber Lake PCI ID (rev2)
Date: Thu, 27 Sep 2018 01:58:12 -0000 [thread overview]
Message-ID: <20180927015812.16062.69428@emeril.freedesktop.org> (raw)
In-Reply-To: <20180927010650.22731-1-jose.souza@intel.com>
== Series Details ==
Series: drm/i915/aml: Add new Amber Lake PCI ID (rev2)
URL : https://patchwork.freedesktop.org/series/50037/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
b83389a0d094 drm/i915/aml: Add new Amber Lake PCI ID
-:52: ERROR:COMPLEX_MACRO: Macros with complex values should be enclosed in parentheses
#52: FILE: include/drm/i915_pciids.h:368:
+#define INTEL_AML_KBL_GT2_IDS(info) \
INTEL_VGA_DEVICE(0x591C, info), /* ULX GT2 */ \
INTEL_VGA_DEVICE(0x87C0, info) /* ULX GT2 */
-:52: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'info' - possible side-effects?
#52: FILE: include/drm/i915_pciids.h:368:
+#define INTEL_AML_KBL_GT2_IDS(info) \
INTEL_VGA_DEVICE(0x591C, info), /* ULX GT2 */ \
INTEL_VGA_DEVICE(0x87C0, info) /* ULX GT2 */
total: 1 errors, 0 warnings, 1 checks, 46 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-09-27 1:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 1:06 [PATCH v2] drm/i915/aml: Add new Amber Lake PCI ID José Roberto de Souza
2018-09-27 1:58 ` Patchwork [this message]
2018-09-27 2:19 ` ✗ Fi.CI.BAT: failure for drm/i915/aml: Add new Amber Lake PCI ID (rev2) Patchwork
2018-10-05 23:01 ` ✓ Fi.CI.BAT: success " Patchwork
2018-10-06 6:02 ` ✓ Fi.CI.IGT: " Patchwork
2018-10-11 18:00 ` [PATCH v2] drm/i915/aml: Add new Amber Lake PCI ID Rodrigo Vivi
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=20180927015812.16062.69428@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jose.souza@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.