From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✗ CI.checksparse: warning for series starting with [CI,1/3] drm: Add drm_vblank_work_flush_all().
Date: Fri, 02 Feb 2024 16:38:34 -0000 [thread overview]
Message-ID: <170689191413.952961.6006434436194223301@5338d5abeb45> (raw)
In-Reply-To: <20240202154423.834991-1-maarten.lankhorst@linux.intel.com>
== Series Details ==
Series: series starting with [CI,1/3] drm: Add drm_vblank_work_flush_all().
URL : https://patchwork.freedesktop.org/series/129477/
State : warning
== 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 1dd92467500a5ead3e44bbdfe15e064dd79b65ef
Sparse version: 0.6.1 (Ubuntu: 0.6.1-2build1)
Fast mode used, each commit won't be checked separately.
+ cleanup
++ stat -c %u:%g /kernel
+ chown -R 1003:1003 /kernel
next prev parent reply other threads:[~2024-02-02 16:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 15:44 [CI 1/3] drm: Add drm_vblank_work_flush_all() Maarten Lankhorst
2024-02-02 15:44 ` [CI 2/3] drm/i915: Use vblank worker to unpin old legacy cursor fb safely Maarten Lankhorst
2024-02-02 15:44 ` [CI 3/3] drm/i915: Use the same vblank worker for atomic unpin Maarten Lankhorst
2024-02-02 16:28 ` ✓ CI.Patch_applied: success for series starting with [CI,1/3] drm: Add drm_vblank_work_flush_all() Patchwork
2024-02-02 16:28 ` ✗ CI.checkpatch: warning " Patchwork
2024-02-02 16:29 ` ✓ CI.KUnit: success " Patchwork
2024-02-02 16:36 ` ✓ CI.Build: " Patchwork
2024-02-02 16:37 ` ✓ CI.Hooks: " Patchwork
2024-02-02 16:38 ` Patchwork [this message]
2024-02-02 17:01 ` ✓ CI.BAT: " Patchwork
2024-02-02 19:30 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2024-02-02 19:30 ` ✗ Fi.CI.SPARSE: " Patchwork
2024-02-02 19:42 ` ✓ Fi.CI.BAT: success " Patchwork
2024-02-02 21:10 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-04-03 9:51 ` ✗ Fi.CI.BUILD: failure for series starting with [CI,1/3] drm: Add drm_vblank_work_flush_all(). (rev2) 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=170689191413.952961.6006434436194223301@5338d5abeb45 \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=maarten.lankhorst@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 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.