From: Jani Nikula <jani.nikula@intel.com>
To: "Knop, Ryszard" <ryszard.knop@intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"De Marchi, Lucas" <lucas.demarchi@intel.com>
Subject: Re: [Intel-xe] ✗ CI.checksparse: warning for xe & i915 display integration, display irqs
Date: Thu, 29 Jun 2023 11:07:12 +0300 [thread overview]
Message-ID: <87jzvmsndb.fsf@intel.com> (raw)
In-Reply-To: <56dbc1319cd4497ef88368539f7d0ee4d5da7185.camel@intel.com>
On Wed, 28 Jun 2023, "Knop, Ryszard" <ryszard.knop@intel.com> wrote:
> On Tue, 2023-06-27 at 12:51 -0300, Lucas De Marchi wrote:
>> On Tue, Jun 27, 2023 at 11:24:04AM -0000, Patchwork wrote:
>> > == Series Details ==
>> >
>> > Series: xe & i915 display integration, display irqs
>> > URL : https://patchwork.freedesktop.org/series/119909/
>> > 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/
>>
>> is the warning because of this redirect?
>
> No, checkpatch/checksparse stages report a warning when "dim sparse" or
> "dim checkpatch" return code != 0.
Now that you're here...
The CI results for xe are different from i915. I have no idea how many
tests there are, and what results I still have to wait for, if any,
before applying.
The result mails or pages don't say where we are, e.g. test 3/6, or what
is still pending.
BR,
Jani.
>
> Ryszard
>
>>
>> Lucas De Marchi
>>
>> > + 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 f135580b567158b23349db5544259730dfb91e78
>> > 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
>> >
>> >
--
Jani Nikula, Intel Open Source Graphics Center
prev parent reply other threads:[~2023-06-29 8:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 10:22 [Intel-xe] [PATCH 0/5] xe & i915 display integration, display irqs Jani Nikula
2023-06-27 10:22 ` [Intel-xe] [PATCH 1/5] drm/i915/uncore: add intel_uncore_regs() helper Jani Nikula
2023-06-27 10:22 ` [Intel-xe] [PATCH 2/5] fixup! drm/xe/display: Implement display support Jani Nikula
2023-06-27 10:22 ` [Intel-xe] [PATCH 3/5] " Jani Nikula
2023-06-27 10:22 ` [Intel-xe] [PATCH 4/5] " Jani Nikula
2023-06-27 16:03 ` Lucas De Marchi
2023-06-27 23:36 ` Jani Nikula
2023-06-28 14:40 ` Lucas De Marchi
2023-06-27 10:22 ` [Intel-xe] [PATCH 5/5] " Jani Nikula
2023-06-27 11:17 ` [Intel-xe] ✓ CI.Patch_applied: success for xe & i915 display integration, display irqs Patchwork
2023-06-27 11:17 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-06-27 11:18 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-06-27 11:22 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-06-27 11:22 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-06-27 11:24 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-06-27 15:51 ` Lucas De Marchi
2023-06-28 11:05 ` Knop, Ryszard
2023-06-29 8:07 ` Jani Nikula [this message]
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=87jzvmsndb.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=ryszard.knop@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.