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 series starting with [1/9] drm/i915: Ignore submit-fences on the same timeline
Date: Fri, 08 May 2020 10:10:31 -0000 [thread overview]
Message-ID: <158893263129.22724.16937837433203736344@emeril.freedesktop.org> (raw)
In-Reply-To: <20200508092933.738-1-chris@chris-wilson.co.uk>
== Series Details ==
Series: series starting with [1/9] drm/i915: Ignore submit-fences on the same timeline
URL : https://patchwork.freedesktop.org/series/77072/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
3db130b5548c drm/i915: Ignore submit-fences on the same timeline
d17611e9e0a3 drm/i915: Pull waiting on an external dma-fence into its routine
fccd141053d3 drm/i915: Prevent using semaphores to chain up to external fences
fe5b438ff7a9 drm/i915: Tidy awaiting on dma-fences
4e705a4d23cc dma-buf: Proxy fence, an unsignaled fence placeholder
-:45: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#45:
new file mode 100644
-:380: CHECK:UNCOMMENTED_DEFINITION: spinlock_t definition without comment
#380: FILE: drivers/dma-buf/st-dma-fence-proxy.c:20:
+ spinlock_t lock;
-:540: WARNING:MEMORY_BARRIER: memory barrier without comment
#540: FILE: drivers/dma-buf/st-dma-fence-proxy.c:180:
+ smp_store_mb(container_of(cb, struct simple_cb, cb)->seen, true);
total: 0 errors, 2 warnings, 1 checks, 1043 lines checked
d5504a1bf6f5 drm/syncobj: Allow use of dma-fence-proxy
61b47826215b drm/i915/gem: Teach execbuf how to wait on future syncobj
f44784ab7169 drm/i915/gem: Allow combining submit-fences with syncobj
96dc49eecf66 drm/i915/gt: Declare when we enabled timeslicing
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-05-08 10:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 9:29 [Intel-gfx] [PATCH 1/9] drm/i915: Ignore submit-fences on the same timeline Chris Wilson
2020-05-08 9:29 ` [Intel-gfx] [PATCH 2/9] drm/i915: Pull waiting on an external dma-fence into its routine Chris Wilson
2020-05-08 10:19 ` Mika Kuoppala
2020-05-08 10:26 ` Chris Wilson
2020-05-08 10:27 ` Chris Wilson
2020-05-08 11:08 ` Mika Kuoppala
2020-05-08 9:29 ` [Intel-gfx] [PATCH 3/9] drm/i915: Prevent using semaphores to chain up to external fences Chris Wilson
2020-05-08 15:37 ` Mika Kuoppala
2020-05-08 15:43 ` Chris Wilson
2020-05-08 15:44 ` Mika Kuoppala
2020-05-08 15:56 ` Chris Wilson
2020-05-08 9:29 ` [Intel-gfx] [PATCH 4/9] drm/i915: Tidy awaiting on dma-fences Chris Wilson
2020-05-08 15:50 ` Mika Kuoppala
2020-05-08 15:58 ` Chris Wilson
2020-05-08 9:29 ` [Intel-gfx] [PATCH 5/9] dma-buf: Proxy fence, an unsignaled fence placeholder Chris Wilson
2020-05-08 9:29 ` [Intel-gfx] [PATCH 6/9] drm/syncobj: Allow use of dma-fence-proxy Chris Wilson
2020-05-08 9:29 ` [Intel-gfx] [PATCH 7/9] drm/i915/gem: Teach execbuf how to wait on future syncobj Chris Wilson
2020-05-08 9:29 ` [Intel-gfx] [PATCH 8/9] drm/i915/gem: Allow combining submit-fences with syncobj Chris Wilson
2020-05-08 9:29 ` [Intel-gfx] [PATCH 9/9] drm/i915/gt: Declare when we enabled timeslicing Chris Wilson
2020-05-08 9:57 ` [Intel-gfx] [PATCH 1/9] drm/i915: Ignore submit-fences on the same timeline Mika Kuoppala
2020-05-08 10:09 ` Chris Wilson
2020-05-08 11:11 ` Mika Kuoppala
2020-05-08 10:10 ` Patchwork [this message]
2020-05-08 10:34 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/9] " Patchwork
2020-05-08 12:27 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=158893263129.22724.16937837433203736344@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.