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: <D7AAOSNDJV11.AXVF80Z934BK@kernel.org>
Date: Fri, 24 Jan 2025 14:16:52 +0200
From: "Jarkko Sakkinen" <jarkko@...nel.org>
To: "Laurent Pinchart" <laurent.pinchart@...asonboard.com>,
 Leonardo BrĂ¡s <leobras.c@...il.com>
Cc: "Vignesh Raman" <vignesh.raman@...labora.com>,
 <kernelci@...ts.linux.dev>, <linuxtv-ci@...uxtv.org>,
 <dave.pigott@...labora.com>, <mripard@...nel.org>,
 <linux-kernel@...r.kernel.org>, <dri-devel@...ts.freedesktop.org>,
 <linux-kselftest@...r.kernel.org>, <gustavo.padovan@...labora.com>,
 <pawiecz@...labora.com>, <spbnick@...il.com>, <tales.aparecida@...il.com>,
 <workflows@...r.kernel.org>, <skhan@...uxfoundation.org>,
 <kunit-dev@...glegroups.com>, <nfraprado@...labora.com>,
 <davidgow@...gle.com>, <cocci@...ia.fr>, <Julia.Lawall@...ia.fr>,
 <laura.nao@...labora.com>, <kernel@...labora.com>,
 <torvalds@...uxfoundation.org>, <gregkh@...uxfoundation.org>,
 <daniels@...labora.com>, <helen.koike@...labora.com>,
 <shreeya.patel@...labora.com>, <denys.f@...labora.com>,
 <nicolas.dufresne@...labora.com>, <louis.chauvet@...tlin.com>,
 <hamohammed.sa@...il.com>, <melissa.srw@...il.com>, <simona@...ll.ch>,
 <airlied@...il.com>, <Tim.Bird@...y.com>, <broonie@...nel.org>,
 <groeck@...gle.com>, <rdunlap@...radead.org>, <geert@...ux-m68k.org>,
 <michel.daenzer@...lbox.org>, <sakari.ailus@....fi>
Subject: Re: [PATCH v2 0/5] kci-gitlab: Introducing GitLab-CI Pipeline for
 Kernel Testing

On Fri Jan 24, 2025 at 10:12 AM EET, Laurent Pinchart wrote:
> Gitlab as an open-source software project (the community edition) is one
> thing, but can we please avoid advertising specific proprietary services
> in the kernel documentation ?

I don't think we should have any of this in the mainline kernel.

One angle is that "no regressions rule" applies also to the shenanigans.

Do we really spend energy on this proprietary crap to the eternity?

BR, Jarkko

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ