From: kernel test robot <lkp@intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
kbuild-all@lists.01.org, matthew.auld@intel.com
Subject: [Intel-gfx] [RFC PATCH] drm/i915: prev_deps() can be static
Date: Thu, 16 Dec 2021 19:06:32 +0800 [thread overview]
Message-ID: <20211216110632.GA39683@7c79fadf3f6c> (raw)
In-Reply-To: <20211215103611.777665-2-thomas.hellstrom@linux.intel.com>
drivers/gpu/drm/i915/gem/i915_gem_ttm_move.c:634:5: warning: symbol 'prev_deps' was not declared. Should it be static?
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
i915_gem_ttm_move.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/i915/gem/i915_gem_ttm_move.c b/drivers/gpu/drm/i915/gem/i915_gem_ttm_move.c
index 09463874ef24e7..e2f679be4e4517 100644
--- a/drivers/gpu/drm/i915/gem/i915_gem_ttm_move.c
+++ b/drivers/gpu/drm/i915/gem/i915_gem_ttm_move.c
@@ -631,8 +631,8 @@ __i915_ttm_move(struct ttm_buffer_object *bo,
return fence;
}
-int prev_deps(struct ttm_buffer_object *bo, struct ttm_operation_ctx *ctx,
- struct i915_deps *deps)
+static int prev_deps(struct ttm_buffer_object *bo, struct ttm_operation_ctx *ctx,
+ struct i915_deps *deps)
{
int ret;
next prev parent reply other threads:[~2021-12-16 11:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 10:36 [Intel-gfx] [PATCH 0/7] drm/i915: Asynchronous vma unbinding Thomas Hellström
2021-12-15 10:36 ` [Intel-gfx] [PATCH 1/7] drm/i915: Avoid using the i915_fence_array when collecting dependencies Thomas Hellström
2021-12-15 17:08 ` kernel test robot
2021-12-15 17:49 ` kernel test robot
2021-12-16 11:06 ` kernel test robot [this message]
2021-12-16 11:10 ` kernel test robot
2021-12-15 10:36 ` [Intel-gfx] [PATCH 2/7] drm/i915: Break out the i915_deps utility Thomas Hellström
2021-12-15 11:08 ` Jani Nikula
2021-12-15 10:36 ` [Intel-gfx] [PATCH 3/7] drm/i915: Require the vm mutex for i915_vma_bind() Thomas Hellström
2021-12-15 10:36 ` [Intel-gfx] [PATCH 4/7] drm/i915: Initial introduction of vma resources Thomas Hellström
2021-12-15 10:36 ` [Intel-gfx] [PATCH 5/7] drm/i915: Use the vma resource as argument for gtt binding / unbinding Thomas Hellström
2021-12-15 10:36 ` [Intel-gfx] [PATCH 6/7] drm/i915: Use vma resources for async unbinding Thomas Hellström
2021-12-15 10:36 ` [Intel-gfx] [PATCH 7/7] drm/i915: Use struct vma_resource instead of struct vma_snapshot Thomas Hellström
2021-12-15 15:56 ` kernel test robot
2021-12-15 18:50 ` kernel test robot
2021-12-15 11:39 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Asynchronous vma unbinding Patchwork
2021-12-15 11:40 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-12-15 12:04 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-12-15 14:19 ` [Intel-gfx] ✗ Fi.CI.IGT: 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=20211216110632.GA39683@7c79fadf3f6c \
--to=lkp@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kbuild-all@lists.01.org \
--cc=matthew.auld@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox