From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Asahi Lina" <lina@asahilina.net>
Cc: intel-xe@lists.freedesktop.org
Subject: ✓ CI.checksparse: success for drm/gpuvm: Add support for single-page-filled mappings
Date: Sun, 02 Feb 2025 14:42:52 -0000 [thread overview]
Message-ID: <173850737231.4012540.10370445810165368079@b555e5b46a47> (raw)
In-Reply-To: <20250202-gpuvm-single-page-v1-0-8cbd44fdcbd4@asahilina.net>
== Series Details ==
Series: drm/gpuvm: Add support for single-page-filled mappings
URL : https://patchwork.freedesktop.org/series/144229/
State : success
== Summary ==
+ trap cleanup EXIT
+ KERNEL=/kernel
+ MT=/root/linux/maintainer-tools
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools /root/linux/maintainer-tools
Cloning into '/root/linux/maintainer-tools'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ make -C /root/linux/maintainer-tools
make: Entering directory '/root/linux/maintainer-tools'
cc -O2 -g -Wextra -o remap-log remap-log.c
make: Leaving directory '/root/linux/maintainer-tools'
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ /root/linux/maintainer-tools/dim sparse --fast 01f54d1da1ffffff78047186f62b5916dfd43939
Sparse version: 0.6.4 (Ubuntu: 0.6.4-4ubuntu3)
Fast mode used, each commit won't be checked separately.
Okay!
+ cleanup
++ stat -c %u:%g /kernel
+ chown -R 1003:1003 /kernel
next prev parent reply other threads:[~2025-02-02 14:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-02 13:34 [PATCH 0/4] drm/gpuvm: Add support for single-page-filled mappings Asahi Lina
2025-02-02 13:34 ` [PATCH 1/4] drm/gpuvm: Add a flags argument to drm_gpuvm_sm_map[_*] Asahi Lina
2025-02-02 13:34 ` [PATCH 2/4] drm/gpuvm: Plumb through flags into drm_gpuva_op_map Asahi Lina
2025-02-02 13:34 ` [PATCH 3/4] drm/gpuvm: Add DRM_GPUVA_SINGLE_PAGE flag and logic Asahi Lina
2025-02-02 13:34 ` [PATCH 4/4] drm/gpuvm: Plumb through flags into drm_gpuva_init Asahi Lina
2025-02-02 14:21 ` ✓ CI.Patch_applied: success for drm/gpuvm: Add support for single-page-filled mappings Patchwork
2025-02-02 14:21 ` ✓ CI.checkpatch: " Patchwork
2025-02-02 14:22 ` ✓ CI.KUnit: " Patchwork
2025-02-02 14:39 ` ✓ CI.Build: " Patchwork
2025-02-02 14:41 ` ✓ CI.Hooks: " Patchwork
2025-02-02 14:42 ` Patchwork [this message]
2025-02-02 15:02 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-02 16:12 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-02 17:49 ` Asahi Lina
2025-02-02 18:53 ` [PATCH 0/4] " Danilo Krummrich
2025-02-02 23:56 ` Asahi Lina
2025-02-03 9:21 ` Boris Brezillon
2025-02-03 11:23 ` Liviu Dudau
2025-02-03 12:12 ` Boris Brezillon
2025-02-03 12:17 ` Matthew Auld
2025-02-03 13:46 ` Asahi Lina
2025-02-03 17:13 ` Boris Brezillon
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=173850737231.4012540.10370445810165368079@b555e5b46a47 \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=lina@asahilina.net \
/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