From: Patchwork <patchwork@emeril.freedesktop.org>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915: Store the BIT(engine->id) as the engine's mask
Date: Sat, 02 Mar 2019 10:30:02 -0000 [thread overview]
Message-ID: <20190302103002.17184.67624@emeril.freedesktop.org> (raw)
In-Reply-To: <20190302100635.3916-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [1/2] drm/i915: Store the BIT(engine->id) as the engine's mask
URL : https://patchwork.freedesktop.org/series/57458/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
01293d6eb866 drm/i915: Store the BIT(engine->id) as the engine's mask
-:1549: CHECK:SPACING: No space is necessary after a cast
#1549: FILE: drivers/gpu/drm/i915/intel_device_info.c:741:
+ BUILD_BUG_ON(BITS_PER_TYPE(intel_engine_mask_t) < I915_NUM_ENGINES);
total: 0 errors, 0 warnings, 1 checks, 2101 lines checked
dd3eb7ff5488 drm/i915: Remove last traces of exec-id (GEM_BUSY)
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-03-02 10:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-02 10:06 Busy ABI bump Chris Wilson
2019-03-02 10:06 ` [PATCH 1/2] drm/i915: Store the BIT(engine->id) as the engine's mask Chris Wilson
2019-03-05 14:44 ` Tvrtko Ursulin
2019-03-05 14:59 ` Chris Wilson
2019-03-02 10:06 ` [PATCH 2/2] drm/i915: Remove last traces of exec-id (GEM_BUSY) Chris Wilson
2019-03-05 14:47 ` Tvrtko Ursulin
2019-03-05 15:49 ` Chris Wilson
2019-03-02 10:30 ` Patchwork [this message]
2019-03-02 10:31 ` ✗ Fi.CI.SPARSE: warning for series starting with [1/2] drm/i915: Store the BIT(engine->id) as the engine's mask Patchwork
2019-03-02 11:01 ` ✓ Fi.CI.BAT: success " Patchwork
2019-03-02 15:41 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-03-02 15:44 ` Chris Wilson
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=20190302103002.17184.67624@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.