From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Asynchronous vma unbinding (rev7)
Date: Mon, 10 Jan 2022 21:10:53 -0000 [thread overview]
Message-ID: <164184905306.28742.16801545187996637425@emeril.freedesktop.org> (raw)
In-Reply-To: <20220110172219.107131-1-thomas.hellstrom@linux.intel.com>
== Series Details ==
Series: drm/i915: Asynchronous vma unbinding (rev7)
URL : https://patchwork.freedesktop.org/series/98055/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
fa2206c87130 drm/i915: Initial introduction of vma resources
-:249: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#249:
new file mode 100644
total: 0 errors, 1 warnings, 0 checks, 625 lines checked
1191590313f3 drm/i915: Use the vma resource as argument for gtt binding / unbinding
98debb352edc drm/i915: Don't pin the object pages during pending vma binds
402bca0f34dc drm/i915: Use vma resources for async unbinding
-:596: CHECK:MACRO_ARG_REUSE: Macro argument reuse '_node' - possible side-effects?
#596: FILE: drivers/gpu/drm/i915/i915_vma_resource.c:37:
+#define VMA_RES_LAST(_node) ((_node)->start + (_node)->node_size - 1)
total: 0 errors, 0 warnings, 1 checks, 941 lines checked
8adfa6f048ac drm/i915: Asynchronous migration selftest
b66f2c830d70 drm/i915: Use struct vma_resource instead of struct vma_snapshot
-:614: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#614:
deleted file mode 100644
total: 0 errors, 1 warnings, 0 checks, 507 lines checked
next prev parent reply other threads:[~2022-01-10 21:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 17:22 [PATCH v7 0/6] drm/i915: Asynchronous vma unbinding Thomas Hellström
2022-01-10 17:22 ` [Intel-gfx] " Thomas Hellström
2022-01-10 17:22 ` [PATCH v7 1/6] drm/i915: Initial introduction of vma resources Thomas Hellström
2022-01-10 17:22 ` [Intel-gfx] " Thomas Hellström
2022-01-10 17:22 ` [PATCH v7 2/6] drm/i915: Use the vma resource as argument for gtt binding / unbinding Thomas Hellström
2022-01-10 17:22 ` [Intel-gfx] " Thomas Hellström
2022-01-10 17:22 ` [PATCH v7 3/6] drm/i915: Don't pin the object pages during pending vma binds Thomas Hellström
2022-01-10 17:22 ` [Intel-gfx] " Thomas Hellström
2022-01-10 17:22 ` [PATCH v7 4/6] drm/i915: Use vma resources for async unbinding Thomas Hellström
2022-01-10 17:22 ` [Intel-gfx] " Thomas Hellström
2022-01-17 21:07 ` Robert Beckett
2022-01-18 9:06 ` Thomas Hellström
2022-01-10 17:22 ` [PATCH v7 5/6] drm/i915: Asynchronous migration selftest Thomas Hellström
2022-01-10 17:22 ` [Intel-gfx] " Thomas Hellström
2022-01-10 17:22 ` [PATCH v7 6/6] drm/i915: Use struct vma_resource instead of struct vma_snapshot Thomas Hellström
2022-01-10 17:22 ` [Intel-gfx] " Thomas Hellström
2022-01-10 21:10 ` Patchwork [this message]
2022-01-10 21:12 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Asynchronous vma unbinding (rev7) Patchwork
2022-01-10 21:42 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-01-11 4:07 ` [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=164184905306.28742.16801545187996637425@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=thomas.hellstrom@linux.intel.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.