From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Dave Airlie <airlied@gmail.com>
Cc: Tomeu Vizoso <tomeu.vizoso@collabora.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Daniel Vetter <daniel@ffwll.ch>, Jonathan Corbet <corbet@lwn.net>,
Rob Clark <robdclark@gmail.com>, Sean Paul <sean@poorly.run>,
Abhinav Kumar <quic_abhinavk@quicinc.com>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
freedreno <freedreno@lists.freedesktop.org>
Subject: Re: Adding CI results to the kernel tree was Re: [RFC v2] drm/msm: Add initial ci/ subdirectory
Date: Wed, 11 May 2022 08:22:56 +0200 [thread overview]
Message-ID: <YntWQIXSqMCd6TYV@kroah.com> (raw)
In-Reply-To: <CAPM=9tzLR-wsLhg2ikGjoK06s-ju5XWa1rtPPiUpN=pwD1vgtA@mail.gmail.com>
On Wed, May 11, 2022 at 03:06:47PM +1000, Dave Airlie wrote:
> > And use it to store expectations about what the drm/msm driver is
> > supposed to pass in the IGT test suite.
>
> I wanted to loop in Linus/Greg to see if there are any issues raised
> by adding CI results file to the tree in their minds, or if any other
> subsystem has done this already, and it's all fine.
Why does the results need to be added to the tree? Shouldn't they be
either "all is good" or "constantly changing and a constant churn"?
> I think this is a good thing after our Mesa experience, but Mesa has a
> lot tighter integration here, so I want to get some more opinions
> outside the group.
For systems that have "tight integration" this might make sense as proof
that all is working for a specific commit, but I can't see how this will
help the kernel out much.
What are you going to do with these results being checked in all the
time?
thanks,
greg k-h
next prev parent reply other threads:[~2022-05-11 6:23 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 7:01 [RFC] drm/msm: Add initial ci/ subdirectory Tomeu Vizoso
2022-05-10 14:13 ` [RFC v2] " Tomeu Vizoso
2022-05-10 19:39 ` [Freedreno] " Jessica Zhang
2022-05-10 20:25 ` Rob Clark
2022-05-11 17:12 ` Daniel Vetter
2022-05-11 17:46 ` Rob Clark
2022-05-11 19:14 ` Daniel Vetter
2022-05-11 20:32 ` Rob Clark
2022-05-11 21:09 ` Daniel Vetter
2022-05-12 13:28 ` Tomeu Vizoso
2022-05-12 14:02 ` Daniel Vetter
2022-05-11 4:25 ` Tomeu Vizoso
2022-05-11 5:06 ` Adding CI results to the kernel tree was " Dave Airlie
2022-05-11 6:22 ` Greg Kroah-Hartman [this message]
2022-05-11 10:26 ` Michel Dänzer
2022-05-11 11:50 ` Greg Kroah-Hartman
2022-05-11 13:33 ` [Freedreno] " Rob Clark
2022-05-11 16:43 ` Daniel Vetter
2022-05-11 17:23 ` Rob Clark
2022-05-12 2:24 ` Theodore Ts'o
2022-05-11 17:33 ` Linus Torvalds
2022-05-11 18:39 ` Rob Clark
2022-05-11 19:08 ` Linus Torvalds
2022-05-11 19:12 ` Linus Torvalds
2022-05-11 20:14 ` [Freedreno] " Rob Clark
2022-05-11 20:06 ` Rob Clark
2022-05-11 19:39 ` Daniel Vetter
2022-05-11 6:15 ` [RFC v3] " Tomeu Vizoso
2022-05-11 13:20 ` Rob Clark
2022-05-11 14:03 ` Tomeu Vizoso
2022-05-17 8:16 ` [RFC v4] drm: " Tomeu Vizoso
2022-05-17 9:18 ` Neil Armstrong
2022-05-17 9:24 ` Tomeu Vizoso
2022-07-26 18:16 ` [PATCH v5] " Tomeu Vizoso
2022-07-29 15:43 ` Rob Clark
2022-08-10 18:24 ` Rodrigo Siqueira Jordao
2022-08-10 22:08 ` Rob Clark
2022-08-11 10:10 ` Tomeu Vizoso
2022-08-16 15:37 ` [PATCH v6] " Tomeu Vizoso
2022-08-29 9:31 ` [PATCH v7] " Tomeu Vizoso
2022-09-09 14:15 ` [PATCH v8] " Tomeu Vizoso
2022-09-12 7:29 ` [PATCH v9] " Tomeu Vizoso
2022-10-14 17:10 ` Rob Clark
2022-10-24 22:06 ` Jessica Zhang
[not found] ` <CAPj87rMYW1xZdacZ1Y0qk+D9xpqsqE+cwbQ1j1nZ7S+RKpzOoQ@mail.gmail.com>
2022-10-25 7:32 ` [PATCH v8] " Daniel Vetter
2022-10-25 15:06 ` Daniel Stone
2022-05-11 14:26 ` [RFC] drm/msm: " Jani Nikula
2022-05-11 14:41 ` Rob Clark
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=YntWQIXSqMCd6TYV@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=airlied@gmail.com \
--cc=corbet@lwn.net \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
--cc=tomeu.vizoso@collabora.com \
--cc=torvalds@linux-foundation.org \
--cc=tzimmermann@suse.de \
/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).