From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [Intel-gfx] [PATCH 0/5] drm/i915: i915_drv.h > i915_gem.h cleanup
Date: Mon, 5 Sep 2022 18:00:48 +0300 [thread overview]
Message-ID: <cover.1662390010.git.jani.nikula@intel.com> (raw)
Some more i915_drv.h cleanup, move the i915_gem.h stuff there.
Jani Nikula (5):
drm/i915: remove unused macro I915_GTT_OFFSET_NONE
drm/i915: remove unused i915_gem_set_global_seqno() declaration
drm/i915: un-inline i915_gem_drain_workqueue()
drm/i915: un-inline i915_gem_drain_freed_objects()
drm/i915: split out i915_gem.c declarations to i915_gem.h
drivers/gpu/drm/i915/i915_drv.h | 75 ---------------------------------
drivers/gpu/drm/i915/i915_gem.c | 37 ++++++++++++++++
drivers/gpu/drm/i915/i915_gem.h | 43 +++++++++++++++++++
3 files changed, 80 insertions(+), 75 deletions(-)
--
2.34.1
next reply other threads:[~2022-09-05 15:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 15:00 Jani Nikula [this message]
2022-09-05 15:00 ` [Intel-gfx] [PATCH 1/5] drm/i915: remove unused macro I915_GTT_OFFSET_NONE Jani Nikula
2022-09-05 15:00 ` [Intel-gfx] [PATCH 2/5] drm/i915: remove unused i915_gem_set_global_seqno() declaration Jani Nikula
2022-09-05 15:00 ` [Intel-gfx] [PATCH 3/5] drm/i915: un-inline i915_gem_drain_workqueue() Jani Nikula
2022-09-05 15:00 ` [Intel-gfx] [PATCH 4/5] drm/i915: un-inline i915_gem_drain_freed_objects() Jani Nikula
2022-09-05 15:00 ` [Intel-gfx] [PATCH 5/5] drm/i915: split out i915_gem.c declarations to i915_gem.h Jani Nikula
2022-09-05 15:58 ` Tvrtko Ursulin
2022-09-06 13:58 ` Jani Nikula
2022-09-05 15:22 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: i915_drv.h > i915_gem.h cleanup Patchwork
2022-09-05 15:37 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-09-05 23:23 ` [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=cover.1662390010.git.jani.nikula@intel.com \
--to=jani.nikula@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 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.