From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [PATCH 0/4] drm/xe: Silence a number of sparse warnings
Date: Tue, 9 Jan 2024 12:24:01 +0100 [thread overview]
Message-ID: <20240109112405.108136-1-thomas.hellstrom@linux.intel.com> (raw)
Sparse complains about a number of missing or conflicting __iomem
annotations. Fix them.
Thomas Hellström (4):
drm/xe: Use __iomem for the regs pointer
drm/xe: Annotate xe_mem_region::mapping with __iomem
drm/xe: Annotate multiple mmio pointers with __iomem
drm/xe: Annotate xe_ttm_stolen_mgr::mapping with __iomem
drivers/gpu/drm/xe/xe_bo.c | 4 ++--
drivers/gpu/drm/xe/xe_device_types.h | 8 ++++----
drivers/gpu/drm/xe/xe_mmio.c | 2 +-
drivers/gpu/drm/xe/xe_ttm_stolen_mgr.c | 4 ++--
4 files changed, 9 insertions(+), 9 deletions(-)
--
2.43.0
next reply other threads:[~2024-01-09 11:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 11:24 Thomas Hellström [this message]
2024-01-09 11:24 ` [PATCH 1/4] drm/xe: Use __iomem for the regs pointer Thomas Hellström
2024-01-09 14:48 ` Lucas De Marchi
2024-01-09 11:24 ` [PATCH 2/4] drm/xe: Annotate xe_mem_region::mapping with __iomem Thomas Hellström
2024-01-09 14:52 ` Lucas De Marchi
2024-01-09 11:24 ` [PATCH 3/4] drm/xe: Annotate multiple mmio pointers " Thomas Hellström
2024-01-09 14:53 ` Lucas De Marchi
2024-01-09 15:27 ` Matt Roper
2024-01-09 11:24 ` [PATCH 4/4] drm/xe: Annotate xe_ttm_stolen_mgr::mapping " Thomas Hellström
2024-01-09 14:55 ` Lucas De Marchi
2024-01-09 13:01 ` ✓ CI.Patch_applied: success for drm/xe: Silence a number of sparse warnings Patchwork
2024-01-09 13:01 ` ✗ CI.checkpatch: warning " Patchwork
2024-01-09 13:02 ` ✓ CI.KUnit: success " Patchwork
2024-01-09 13:10 ` ✓ CI.Build: " Patchwork
2024-01-09 13:10 ` ✓ CI.Hooks: " Patchwork
2024-01-09 13:11 ` ✓ CI.checksparse: " Patchwork
2024-01-09 13:46 ` ✓ CI.BAT: " 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=20240109112405.108136-1-thomas.hellstrom@linux.intel.com \
--to=thomas.hellstrom@linux.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 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.