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: Copy across scheduler behaviour flags across submit fences (rev2)
Date: Wed, 04 Dec 2019 12:18:00 -0000 [thread overview]
Message-ID: <157546188085.12195.7788879640475494694@emeril.freedesktop.org> (raw)
In-Reply-To: <20191204112633.3649206-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: drm/i915: Copy across scheduler behaviour flags across submit fences (rev2)
URL : https://patchwork.freedesktop.org/series/70107/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
d65868d85183 drm/i915: Copy across scheduler behaviour flags across submit fences
-:185: ERROR:SPACING: spaces required around that '=' (ctx:WxV)
#185: FILE: drivers/gpu/drm/i915/i915_request.c:1048:
+ err =__emit_semaphore_wait(to, from, from->fence.seqno - 1);
^
total: 1 errors, 0 warnings, 0 checks, 172 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:[~2019-12-04 12:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 11:26 [Intel-gfx] [PATCH v2] drm/i915: Copy across scheduler behaviour flags across submit fences Chris Wilson
2019-12-04 12:18 ` Patchwork [this message]
2019-12-04 13:33 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Copy across scheduler behaviour flags across submit fences (rev2) Patchwork
2019-12-04 14:12 ` [Intel-gfx] [PATCH v2] drm/i915: Copy across scheduler behaviour flags across submit fences Tvrtko Ursulin
2019-12-04 14:15 ` Chris Wilson
2019-12-04 14:19 ` Chris Wilson
2019-12-04 20:11 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Copy across scheduler behaviour flags across submit fences (rev3) Patchwork
2019-12-04 20:34 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " 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=157546188085.12195.7788879640475494694@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.