From: Maxime Ripard <mripard@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Vignesh Raman <vignesh.raman@collabora.com>,
dri-devel@lists.freedesktop.org, daniels@collabora.com,
helen.fornazier@gmail.com, airlied@gmail.com,
simona.vetter@ffwll.ch, robdclark@gmail.com,
guilherme.gallo@collabora.com, sergi.blanch.torne@collabora.com,
valentine.burley@collabora.com, lumag@kernel.org,
quic_abhinavk@quicinc.com, maarten.lankhorst@linux.intel.com,
tzimmermann@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 2/3] drm/ci: Add jobs to validate devicetrees
Date: Mon, 31 Mar 2025 09:53:47 +0200 [thread overview]
Message-ID: <20250331-amphibian-hopping-bobcat-e19a0b@houat> (raw)
In-Reply-To: <v4dhuuuvfk63bakncz43z3ndjdze5ac7nrv6qvtpdnonfpetsx@5hh3vzcj336x>
[-- Attachment #1: Type: text/plain, Size: 847 bytes --]
On Sun, Mar 30, 2025 at 08:06:45PM +0300, Dmitry Baryshkov wrote:
> On Thu, Mar 27, 2025 at 09:31:11PM +0530, Vignesh Raman wrote:
> > Add jobs to run dt_binding_check and dtbs_check. If warnings are seen,
> > exit with a non-zero error code while configuring them as warning in
> > the GitLab CI pipeline.
>
> Can it really succeed or is it going to be an always-failing job? The
> dt_binding_check generally succeed, dtbs_check generates tons of
> warnings. We are trying to make progress there, but it's still very far
> from being achevable.
It depends on the platforms I guess. Some are 100% covered and any
warning should be treated as a failure, and some have not started the
effort.
I guess we could solve it with some kind of expectation list, but I do
wonder if it's something *we* should be focusing on :)
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-03-31 7:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 16:01 [PATCH v1 0/3] drm/ci: Add devicetree validation and KUnit tests Vignesh Raman
2025-03-27 16:01 ` [PATCH v1 1/3] drm/ci: force use of BFD linker Vignesh Raman
2025-03-27 16:01 ` [PATCH v1 2/3] drm/ci: Add jobs to validate devicetrees Vignesh Raman
2025-03-30 17:06 ` Dmitry Baryshkov
2025-03-31 7:53 ` Maxime Ripard [this message]
2025-03-31 7:55 ` Dmitry Baryshkov
2025-04-01 2:15 ` Vignesh Raman
2025-04-01 1:56 ` Vignesh Raman
2025-04-01 15:14 ` Maxime Ripard
2025-03-27 16:01 ` [PATCH v1 3/3] drm/ci: Add jobs to run KUnit tests Vignesh Raman
2025-03-28 15:10 ` Maxime Ripard
2025-04-01 2:17 ` Vignesh Raman
2025-04-07 12:35 ` Maxime Ripard
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=20250331-amphibian-hopping-bobcat-e19a0b@houat \
--to=mripard@kernel.org \
--cc=airlied@gmail.com \
--cc=daniels@collabora.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=guilherme.gallo@collabora.com \
--cc=helen.fornazier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sergi.blanch.torne@collabora.com \
--cc=simona.vetter@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=valentine.burley@collabora.com \
--cc=vignesh.raman@collabora.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
all inboxes | Powered by JetHome®