From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Juha-Pekka Heikkila" <juhapekka.heikkila@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915/display: Add smem fallback allocation for dpt
Date: Fri, 06 May 2022 14:14:35 -0000 [thread overview]
Message-ID: <165184647590.18818.4093426650291261553@emeril.freedesktop.org> (raw)
In-Reply-To: <20220506131109.20942-1-juhapekka.heikkila@gmail.com>
== Series Details ==
Series: series starting with [1/2] drm/i915/display: Add smem fallback allocation for dpt
URL : https://patchwork.freedesktop.org/series/103678/
State : warning
== Summary ==
Error: dim checkpatch failed
cb0cd39c87aa drm/i915/display: Add smem fallback allocation for dpt
5fc338ca8432 drm/i915: Fix i915_vma_pin_iomap()
-:44: CHECK:BRACES: Unbalanced braces around else statement
#44: FILE: drivers/gpu/drm/i915/i915_vma.c:572:
+ else {
-:47: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#47: FILE: drivers/gpu/drm/i915/i915_vma.c:575:
+ i915_gem_object_pin_map_unlocked(vma->obj,
+ I915_MAP_WC);
total: 0 errors, 0 warnings, 2 checks, 73 lines checked
next prev parent reply other threads:[~2022-05-06 14:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 13:11 [Intel-gfx] [PATCH 1/2] drm/i915/display: Add smem fallback allocation for dpt Juha-Pekka Heikkila
2022-05-06 13:11 ` [Intel-gfx] [PATCH 2/2] drm/i915: Fix i915_vma_pin_iomap() Juha-Pekka Heikkila
2022-05-11 11:06 ` Matthew Auld
2022-05-06 14:14 ` Patchwork [this message]
2022-05-06 14:23 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915/display: Add smem fallback allocation for dpt Patchwork
2022-05-06 17:22 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-05-11 10:41 ` [Intel-gfx] [PATCH 1/2] " Matthew Auld
2022-05-20 11:23 ` Juha-Pekka Heikkilä
2022-05-20 11:45 ` Matthew Auld
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=165184647590.18818.4093426650291261553@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=juhapekka.heikkila@gmail.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.