From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Lucas De Marchi" <lucas.demarchi@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"DRM XE List" <intel-xe@lists.freedesktop.org>
Cc: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warnings after merge of the drm-xe tree
Date: Wed, 27 Aug 2025 13:30:24 +1000 [thread overview]
Message-ID: <20250827133024.41e3c2ac@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1825 bytes --]
Hi all,
After merging the drm-xe tree, today's linux-next build (htmldocs)
produced these warnings:
Documentation/gpu/driver-uapi:29: include/uapi/drm/xe_drm.h:2078: ERROR: Unexpected indentation. [docutils]
Documentation/gpu/driver-uapi:29: include/uapi/drm/xe_drm.h:2080: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
Documentation/gpu/driver-uapi:29: include/uapi/drm/xe_drm.h:2012: ERROR: Unexpected indentation. [docutils]
Documentation/gpu/driver-uapi:29: include/uapi/drm/xe_drm.h:2196: ERROR: Error in "code-block" directive:
maximum 1 argument(s) allowed, 16 supplied.
.. code-block:: C
struct drm_xe_vm_query_mem_range_attr query = {
.vm_id = vm_id,
.start = 0x100000,
.range = 0x2000,
};
// First ioctl call to get num of mem regions and sizeof each attribute
ioctl(fd, DRM_IOCTL_XE_VM_QUERY_MEM_RANGE_ATTRS, &query);
// Allocate buffer for the memory region attributes
void *ptr = malloc(query.num_mem_ranges * query.sizeof_mem_range_attr);
void *ptr_start = ptr;
query.vector_of_mem_attr = (uintptr_t)ptr;
// Second ioctl call to actually fill the memory attributes
ioctl(fd, DRM_IOCTL_XE_VM_QUERY_MEM_RANGE_ATTRS, &query);
// Iterate over the returned memory region attributes
for (unsigned int i = 0; i < query.num_mem_ranges; ++i) {
struct drm_xe_mem_range_attr *attr = (struct drm_xe_mem_range_attr *)ptr;
// Do something with attr
// Move pointer by one entry
ptr += query.sizeof_mem_range_attr;
}
free(ptr_start); [docutils]
Introduced by commits
231bb0ee7aa5 ("drm/xe/uapi: Add madvise interface")
418807860e94 ("drm/xe/uapi: Add UAPI for querying VMA count and memory attributes")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2025-08-27 3:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250827133024.41e3c2ac@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lucas.demarchi@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;
as well as URLs for NNTP newsgroup(s).