From: Gustavo Sousa <gustavo.sousa@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [PATCH] drm/xe: Remove stale declaration of xe_mmio_probe_vram()
Date: Mon, 22 Jul 2024 16:05:25 -0300 [thread overview]
Message-ID: <20240722190524.71548-2-gustavo.sousa@intel.com> (raw)
The declaration of xe_mmio_probe_vram() became useless since
commit 638d1c79cbf1 ("drm/xe: Promote VRAM initialization function to
own file"). Remove it.
Signed-off-by: Gustavo Sousa <gustavo.sousa@intel.com>
---
drivers/gpu/drm/xe/xe_mmio.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/xe/xe_mmio.h b/drivers/gpu/drm/xe/xe_mmio.h
index 6ae0cc32c651..26551410ecc8 100644
--- a/drivers/gpu/drm/xe/xe_mmio.h
+++ b/drivers/gpu/drm/xe/xe_mmio.h
@@ -22,7 +22,6 @@ u32 xe_mmio_rmw32(struct xe_gt *gt, struct xe_reg reg, u32 clr, u32 set);
int xe_mmio_write32_and_verify(struct xe_gt *gt, struct xe_reg reg, u32 val, u32 mask, u32 eval);
bool xe_mmio_in_range(const struct xe_gt *gt, const struct xe_mmio_range *range, struct xe_reg reg);
-int xe_mmio_probe_vram(struct xe_device *xe);
u64 xe_mmio_read64_2x32(struct xe_gt *gt, struct xe_reg reg);
int xe_mmio_wait32(struct xe_gt *gt, struct xe_reg reg, u32 mask, u32 val, u32 timeout_us,
u32 *out_val, bool atomic);
--
2.45.2
next reply other threads:[~2024-07-22 19:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 19:05 Gustavo Sousa [this message]
2024-07-22 19:11 ` ✓ CI.Patch_applied: success for drm/xe: Remove stale declaration of xe_mmio_probe_vram() Patchwork
2024-07-22 19:11 ` ✓ CI.checkpatch: " Patchwork
2024-07-22 19:11 ` ✗ CI.KUnit: failure " Patchwork
2024-07-22 21:11 ` [PATCH] " Michal Wajdeczko
2024-07-23 13:24 ` ✓ CI.Patch_applied: success for drm/xe: Remove stale declaration of xe_mmio_probe_vram() (rev2) Patchwork
2024-07-23 13:24 ` ✓ CI.checkpatch: " Patchwork
2024-07-23 13:25 ` ✓ CI.KUnit: " Patchwork
2024-07-23 13:37 ` ✓ CI.Build: " Patchwork
2024-07-23 13:40 ` ✓ CI.Hooks: " Patchwork
2024-07-23 13:42 ` ✓ CI.checksparse: " Patchwork
2024-07-23 15:32 ` ✓ CI.FULL: " Patchwork
2024-07-25 23:58 ` Matt Roper
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=20240722190524.71548-2-gustavo.sousa@intel.com \
--to=gustavo.sousa@intel.com \
--cc=intel-xe@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