linux-kernel - Re: [PATCH 1/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CABXOdTcT+szLRMfx=3WFoXDirOmWCY7T+8Q+zZJ=B5GscpDNnQ@mail.gmail.com>
Date: Mon, 4 Mar 2024 11:44:23 -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 9:09 AM Maxime Ripard <mripard@...nel.org> wrote:

[ ...]

>
> And singling out DRM because it regularly allegedly breaks things on
> xtensa or m68k and claiming we're not taking CI seriously because of it
> is completely ridiculous. If the all the subsystems were taking CI as
> seriously as DRM, we would be in a much better place.
>

FWIW:

$ git grep CONFIG_DRM arch/xtensa/ arch/m68k/
arch/m68k/configs/virt_defconfig:CONFIG_DRM=y
arch/m68k/configs/virt_defconfig:CONFIG_DRM_FBDEV_EMULATION=y
arch/m68k/configs/virt_defconfig:CONFIG_DRM_VIRTIO_GPU=y
arch/xtensa/configs/virt_defconfig:CONFIG_DRM=y
arch/xtensa/configs/virt_defconfig:CONFIG_DRM_VGEM=y
arch/xtensa/configs/virt_defconfig:CONFIG_DRM_VIRTIO_GPU=y

If that isn't supported, it might really make sense to declare that
CONFIG_DRM depends on !xtensa and !m68k.

Guenter