From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Chris Wilson" <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Prevent waiting inside ring construction for critical sections (rev3)
Date: Wed, 03 Feb 2021 17:24:06 -0000 [thread overview]
Message-ID: <161237304651.943.13391810467452196913@emeril.freedesktop.org> (raw)
In-Reply-To: <20210203124740.9354-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: drm/i915: Prevent waiting inside ring construction for critical sections (rev3)
URL : https://patchwork.freedesktop.org/series/86644/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
c2a787bb37c7 drm/i915: Prevent waiting inside ring construction for critical sections
-:30: ERROR:SPACING: spaces required around that '=' (ctx:VxW)
#30: FILE: drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c:1263:
+ unsigned long flags= 0;
^
total: 1 errors, 0 warnings, 0 checks, 185 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-02-03 17:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 12:47 [Intel-gfx] [PATCH] drm/i915: Prevent waiting inside ring construction for critical sections Chris Wilson
2021-02-03 14:55 ` [Intel-gfx] [PATCH v2] " Chris Wilson
2021-02-03 15:00 ` [Intel-gfx] [PATCH v3] " Chris Wilson
2021-02-03 16:58 ` [Intel-gfx] [PATCH] " kernel test robot
2021-02-03 16:58 ` kernel test robot
2021-02-03 17:24 ` Patchwork [this message]
2021-02-03 17:55 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Prevent waiting inside ring construction for critical sections (rev3) 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=161237304651.943.13391810467452196913@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/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.