From: Jasmine Newsome <jasmine.newsome@intel.com>
To: Intel-GFX@Lists.FreeDesktop.Org
Subject: [Intel-gfx] [PATCH] drm/i915/gem: Use local pointer ttm for __i915_ttm_move
Date: Tue, 4 Jan 2022 12:36:42 -0800 [thread overview]
Message-ID: <20220104203642.231878-1-jasmine.newsome@intel.com> (raw)
Using local pointer ttm as argument in __i915_ttm_move instead of bo->ttm,
as local pointer was previously assigned to bo->ttm in function.
This will make code a bit more readable.
Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Signed-off-by: Jasmine Newsome <jasmine.newsome@intel.com>
---
drivers/gpu/drm/i915/gem/i915_gem_ttm_move.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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 ee9612a3ee5e..8653855d808b 100644
--- a/drivers/gpu/drm/i915/gem/i915_gem_ttm_move.c
+++ b/drivers/gpu/drm/i915/gem/i915_gem_ttm_move.c
@@ -525,7 +525,7 @@ int i915_ttm_move(struct ttm_buffer_object *bo, bool evict,
return ret;
}
- migration_fence = __i915_ttm_move(bo, ctx, clear, dst_mem, bo->ttm,
+ migration_fence = __i915_ttm_move(bo, ctx, clear, dst_mem, ttm,
dst_rsgt, true, &deps);
i915_deps_fini(&deps);
}
--
2.25.1
next reply other threads:[~2022-01-04 20:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 20:36 Jasmine Newsome [this message]
2022-01-04 21:28 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/gem: Use local pointer ttm for __i915_ttm_move (rev4) Patchwork
2022-01-04 23:30 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
[not found] <20211209000533.1670512-1-jasmine.newsome@intel.com>
2021-12-10 13:32 ` [Intel-gfx] [PATCH] drm/i915/gem: Use local pointer ttm for __i915_ttm_move Hellstrom, Thomas
-- strict thread matches above, loose matches on Subject: below --
2021-12-09 16:23 Jasmine Newsome
2021-12-09 6:33 Jasmine Newsome
2021-12-03 21:49 Jasmine Newsome
2021-12-08 10:10 ` Thomas Hellström (Intel)
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=20220104203642.231878-1-jasmine.newsome@intel.com \
--to=jasmine.newsome@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox