From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Add relocation exceptions for two other platforms (rev3)
Date: Tue, 01 Jun 2021 08:46:46 -0000 [thread overview]
Message-ID: <162253720631.19252.9465343630758107132@emeril.freedesktop.org> (raw)
In-Reply-To: <20210601082847.78389-1-zbigniew.kempczynski@intel.com>
== Series Details ==
Series: drm/i915: Add relocation exceptions for two other platforms (rev3)
URL : https://patchwork.freedesktop.org/series/89594/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
07cc51d80ac1 drm/i915: Add relocation exceptions for two other platforms
-:44: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#44: FILE: drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c:507:
+ if (INTEL_INFO(eb->i915)->require_force_probe &&
+ (IS_ROCKETLAKE(eb->i915) || IS_ALDERLAKE_S(eb->i915) ||
total: 0 errors, 0 warnings, 1 checks, 37 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:[~2021-06-01 8:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 8:28 [PATCH] drm/i915: Add relocation exceptions for two other platforms Zbigniew Kempczyński
2021-06-01 8:28 ` [Intel-gfx] " Zbigniew Kempczyński
2021-06-01 8:46 ` Patchwork [this message]
2021-06-01 9:16 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Add relocation exceptions for two other platforms (rev3) Patchwork
2021-06-01 11:36 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-06-01 12:38 ` Zbigniew Kempczyński
2021-06-01 12:26 ` [Intel-gfx] [PATCH] drm/i915: Add relocation exceptions for two other platforms Jani Nikula
2021-06-01 12:26 ` Jani Nikula
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=162253720631.19252.9465343630758107132@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=zbigniew.kempczynski@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.