[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABXOdTc4MXcjwgGuJb4_69-4OFELD37x0B6oMr=4z=nxZ2HPXQ@mail.gmail.com>
Date: Mon, 4 Mar 2024 07:46:34 -0800
From: Guenter Roeck <groeck@...gle.com>
To: Maxime Ripard <mripard@...nel.org>
Cc: Linus Torvalds <torvalds@...uxfoundation.org>, Nikolai Kondrashov <spbnick@...il.com>,
Helen Koike <helen.koike@...labora.com>, linuxtv-ci@...uxtv.org,
dave.pigott@...labora.com, linux-kernel@...r.kernel.org,
dri-devel@...ts.freedesktop.org, linux-kselftest@...r.kernel.org,
gustavo.padovan@...labora.com, pawiecz@...labora.com,
tales.aparecida@...il.com, workflows@...r.kernel.org,
kernelci@...ts.linux.dev, skhan@...uxfoundation.org,
kunit-dev@...glegroups.com, nfraprado@...labora.com, davidgow@...gle.com,
cocci@...ia.fr, Julia.Lawall@...ia.fr, laura.nao@...labora.com,
ricardo.canuelo@...labora.com, kernel@...labora.com,
gregkh@...uxfoundation.org
Subject: Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
On Mon, Mar 4, 2024 at 1:24 AM Maxime Ripard <mripard@...nel.org> wrote:
[ ... ]
>
> If anything, it's more of a side-effect to the push for COMPILE_TEST
> than anything.
>
If the drm subsystem maintainers don't want people to build it with
COMPILE_TEST while at the same time not limiting it to platforms where
it doesn't even build, I'd suggest making it dependent on
!COMPILE_TEST.
The same applies to all other subsystems where maintainers don't want
build tests to run but also don't want to add restrictions such as
"64-bit only". After all, this was just one example.
Guenter
Powered by blists - more mailing lists