From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Nikolai Kondrashov" <Nikolai.Kondrashov@redhat.com>,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Leonardo Brás" <leobras.c@gmail.com>
Cc: "Vignesh Raman" <vignesh.raman@collabora.com>,
<kernelci@lists.linux.dev>, <linuxtv-ci@linuxtv.org>,
<dave.pigott@collabora.com>, <mripard@kernel.org>,
<linux-kernel@vger.kernel.org>, <dri-devel@lists.freedesktop.org>,
<linux-kselftest@vger.kernel.org>,
<gustavo.padovan@collabora.com>, <pawiecz@collabora.com>,
<spbnick@gmail.com>, <tales.aparecida@gmail.com>,
<workflows@vger.kernel.org>, <skhan@linuxfoundation.org>,
<kunit-dev@googlegroups.com>, <nfraprado@collabora.com>,
<davidgow@google.com>, <cocci@inria.fr>, <Julia.Lawall@inria.fr>,
<laura.nao@collabora.com>, <kernel@collabora.com>,
<torvalds@linuxfoundation.org>, <gregkh@linuxfoundation.org>,
<daniels@collabora.com>, <helen.koike@collabora.com>,
<shreeya.patel@collabora.com>, <denys.f@collabora.com>,
<nicolas.dufresne@collabora.com>, <louis.chauvet@bootlin.com>,
<hamohammed.sa@gmail.com>, <melissa.srw@gmail.com>,
<simona@ffwll.ch>, <airlied@gmail.com>, <Tim.Bird@sony.com>,
<broonie@kernel.org>, <groeck@google.com>,
<rdunlap@infradead.org>, <geert@linux-m68k.org>,
<michel.daenzer@mailbox.org>, <sakari.ailus@iki.fi>
Subject: Re: [cocci] [PATCH v2 0/5] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
Date: Fri, 24 Jan 2025 18:36:00 +0200 [thread overview]
Message-ID: <D7AG776AI2EQ.KLG13BCOXBJL@kernel.org> (raw)
In-Reply-To: <298675d0-ba19-4c87-b00d-57a5e31b05b6@redhat.com>
On Fri Jan 24, 2025 at 3:00 PM EET, Nikolai Kondrashov wrote:
> On 1/24/25 2:16 PM, Jarkko Sakkinen wrote:
> > 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?
>
> This is not getting included into the kernel itself, the contributed code is,
> of course, open-source. And yes it would execute just fine on the fully
> open-source community-edition GitLab. I don't think "no regressions rule"
> should apply here. This is for developers only, and is a template for making
> your own pipeline mostly, with pieces which can be reused.
Ah, OK then it is fine. It was a kernel list so I assumed it was for
kernel.
Then: I don't care about this ;-) I use a different testing tool
(BuildRoot) and a different CI (Woodpecker in my local server).
So go ahead and do what you like...
>
> Nick
BR, Jarkko
WARNING: multiple messages have this Message-ID (diff)
From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Nikolai Kondrashov" <Nikolai.Kondrashov@redhat.com>,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Leonardo Brás" <leobras.c@gmail.com>
Cc: "Vignesh Raman" <vignesh.raman@collabora.com>,
<kernelci@lists.linux.dev>, <linuxtv-ci@linuxtv.org>,
<dave.pigott@collabora.com>, <mripard@kernel.org>,
<linux-kernel@vger.kernel.org>, <dri-devel@lists.freedesktop.org>,
<linux-kselftest@vger.kernel.org>,
<gustavo.padovan@collabora.com>, <pawiecz@collabora.com>,
<spbnick@gmail.com>, <tales.aparecida@gmail.com>,
<workflows@vger.kernel.org>, <skhan@linuxfoundation.org>,
<kunit-dev@googlegroups.com>, <nfraprado@collabora.com>,
<davidgow@google.com>, <cocci@inria.fr>, <Julia.Lawall@inria.fr>,
<laura.nao@collabora.com>, <kernel@collabora.com>,
<torvalds@linuxfoundation.org>, <gregkh@linuxfoundation.org>,
<daniels@collabora.com>, <helen.koike@collabora.com>,
<shreeya.patel@collabora.com>, <denys.f@collabora.com>,
<nicolas.dufresne@collabora.com>, <louis.chauvet@bootlin.com>,
<hamohammed.sa@gmail.com>, <melissa.srw@gmail.com>,
<simona@ffwll.ch>, <airlied@gmail.com>, <Tim.Bird@sony.com>,
<broonie@kernel.org>, <groeck@google.com>,
<rdunlap@infradead.org>, <geert@linux-m68k.org>,
<michel.daenzer@mailbox.org>, <sakari.ailus@iki.fi>
Subject: Re: [PATCH v2 0/5] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing
Date: Fri, 24 Jan 2025 18:36:00 +0200 [thread overview]
Message-ID: <D7AG776AI2EQ.KLG13BCOXBJL@kernel.org> (raw)
In-Reply-To: <298675d0-ba19-4c87-b00d-57a5e31b05b6@redhat.com>
On Fri Jan 24, 2025 at 3:00 PM EET, Nikolai Kondrashov wrote:
> On 1/24/25 2:16 PM, Jarkko Sakkinen wrote:
> > 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?
>
> This is not getting included into the kernel itself, the contributed code is,
> of course, open-source. And yes it would execute just fine on the fully
> open-source community-edition GitLab. I don't think "no regressions rule"
> should apply here. This is for developers only, and is a template for making
> your own pipeline mostly, with pieces which can be reused.
Ah, OK then it is fine. It was a kernel list so I assumed it was for
kernel.
Then: I don't care about this ;-) I use a different testing tool
(BuildRoot) and a different CI (Woodpecker in my local server).
So go ahead and do what you like...
>
> Nick
BR, Jarkko
next prev parent reply other threads:[~2025-01-28 9:13 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 13:53 [cocci] [PATCH v2 0/5] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing Vignesh Raman
2025-01-23 13:53 ` Vignesh Raman
2025-01-23 13:53 ` [cocci] [PATCH v2 1/5] " Vignesh Raman
2025-01-23 13:53 ` Vignesh Raman
2025-01-23 13:53 ` [cocci] [PATCH v2 2/5] MAINTAINERS: Add an entry for ci automated testing Vignesh Raman
2025-01-23 13:53 ` Vignesh Raman
2025-01-23 13:53 ` [cocci] [PATCH v2 3/5] kci-gitlab: Add drm scenario Vignesh Raman
2025-01-23 13:53 ` Vignesh Raman
2025-01-23 20:06 ` [cocci] " Simona Vetter
2025-01-23 20:06 ` Simona Vetter
2025-01-24 12:37 ` [cocci] " Helen Mae Koike Fornazier
2025-01-24 12:37 ` Helen Mae Koike Fornazier
2025-01-24 15:31 ` [cocci] " Simona Vetter
2025-01-24 15:31 ` Simona Vetter
2025-01-27 4:07 ` [cocci] " Vignesh Raman
2025-01-27 4:07 ` Vignesh Raman
2025-01-23 13:53 ` [cocci] [PATCH v2 4/5] kci-gitlab: Add documentation Vignesh Raman
2025-01-23 13:53 ` Vignesh Raman
2025-01-23 13:53 ` [cocci] [PATCH v2 5/5] kci-gitlab: docs: Add images Vignesh Raman
2025-01-23 13:53 ` Vignesh Raman
2025-01-23 15:46 ` [cocci] " Linus Torvalds
2025-01-23 15:46 ` Linus Torvalds
2025-01-23 18:04 ` [cocci] " Nicolas Dufresne
2025-01-23 18:04 ` Nicolas Dufresne
2025-01-27 3:56 ` [cocci] " Vignesh Raman
2025-01-27 3:56 ` Vignesh Raman
2025-01-23 21:30 ` [cocci] [PATCH v2 0/5] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing Jarkko Sakkinen
2025-01-23 21:30 ` Jarkko Sakkinen
2025-01-23 21:31 ` [cocci] " Jarkko Sakkinen
2025-01-23 21:31 ` Jarkko Sakkinen
2025-01-24 12:58 ` [cocci] " Nikolai Kondrashov
2025-01-24 12:58 ` Nikolai Kondrashov
2025-01-24 16:32 ` [cocci] " Jarkko Sakkinen
2025-01-24 16:32 ` Jarkko Sakkinen
2025-01-24 17:04 ` [cocci] " Nikolai Kondrashov
2025-01-24 17:04 ` Nikolai Kondrashov
2025-01-24 17:15 ` [cocci] " Mark Brown
2025-01-24 17:15 ` Mark Brown
2025-01-24 17:34 ` [cocci] " Laurent Pinchart
2025-01-24 17:34 ` Laurent Pinchart
2025-01-24 5:11 ` [cocci] " Leonardo Brás
2025-01-24 5:11 ` Leonardo Brás
2025-01-24 8:12 ` [cocci] " Laurent Pinchart
2025-01-24 8:12 ` Laurent Pinchart
2025-01-24 12:16 ` [cocci] " Jarkko Sakkinen
2025-01-24 12:16 ` Jarkko Sakkinen
2025-01-24 13:00 ` [cocci] " Nikolai Kondrashov
2025-01-24 13:00 ` Nikolai Kondrashov
2025-01-24 14:26 ` [cocci] " Nicolas Dufresne
2025-01-24 14:26 ` Nicolas Dufresne
2025-01-24 15:29 ` [cocci] " Mauro Carvalho Chehab
2025-01-24 15:29 ` Mauro Carvalho Chehab
2025-01-24 19:49 ` [cocci] " Helen Mae Koike Fornazier
2025-01-24 19:49 ` Helen Mae Koike Fornazier
2025-01-24 19:59 ` [cocci] " Bird, Tim
2025-01-24 19:59 ` Bird, Tim
2025-01-27 6:39 ` [cocci] " Mauro Carvalho Chehab
2025-01-27 6:39 ` Mauro Carvalho Chehab
2025-01-24 16:36 ` Jarkko Sakkinen [this message]
2025-01-24 16:36 ` Jarkko Sakkinen
2025-01-24 12:52 ` [cocci] " Mauro Carvalho Chehab
2025-01-24 12:52 ` Mauro Carvalho Chehab
2025-01-24 13:00 ` [cocci] " Laurent Pinchart
2025-01-24 13:00 ` Laurent Pinchart
2025-01-24 15:45 ` [cocci] " Nicolas Dufresne
2025-01-24 15:45 ` Nicolas Dufresne
2025-01-24 21:12 ` [cocci] " Leonardo Brás
2025-01-24 21:12 ` Leonardo Brás
2025-01-27 6:07 ` [cocci] " Laurent Pinchart
2025-01-27 6:07 ` Laurent Pinchart
2025-01-27 7:07 ` [cocci] " Mauro Carvalho Chehab
2025-01-27 7:07 ` Mauro Carvalho Chehab
2025-01-27 14:43 ` [cocci] " Nicolas Dufresne
2025-01-27 14:43 ` Nicolas Dufresne
2025-01-27 16:23 ` [cocci] " Laurent Pinchart
2025-01-27 16:23 ` Laurent Pinchart
2025-01-24 20:50 ` [cocci] " Leonardo Brás
2025-01-24 20:50 ` Leonardo Brás
2025-01-27 7:32 ` [cocci] " Vignesh Raman
2025-01-27 7:32 ` Vignesh Raman
2025-01-27 19:05 ` [cocci] " Leonardo Brás
2025-01-27 19:05 ` Leonardo Brás
2025-01-29 9:32 ` [cocci] " Vignesh Raman
2025-01-29 9:32 ` Vignesh Raman
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=D7AG776AI2EQ.KLG13BCOXBJL@kernel.org \
--to=jarkko@kernel.org \
--cc=Julia.Lawall@inria.fr \
--cc=Nikolai.Kondrashov@redhat.com \
--cc=Tim.Bird@sony.com \
--cc=airlied@gmail.com \
--cc=broonie@kernel.org \
--cc=cocci@inria.fr \
--cc=daniels@collabora.com \
--cc=dave.pigott@collabora.com \
--cc=davidgow@google.com \
--cc=denys.f@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@google.com \
--cc=gustavo.padovan@collabora.com \
--cc=hamohammed.sa@gmail.com \
--cc=helen.koike@collabora.com \
--cc=kernel@collabora.com \
--cc=kernelci@lists.linux.dev \
--cc=kunit-dev@googlegroups.com \
--cc=laura.nao@collabora.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=leobras.c@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linuxtv-ci@linuxtv.org \
--cc=louis.chauvet@bootlin.com \
--cc=melissa.srw@gmail.com \
--cc=michel.daenzer@mailbox.org \
--cc=mripard@kernel.org \
--cc=nfraprado@collabora.com \
--cc=nicolas.dufresne@collabora.com \
--cc=pawiecz@collabora.com \
--cc=rdunlap@infradead.org \
--cc=sakari.ailus@iki.fi \
--cc=shreeya.patel@collabora.com \
--cc=simona@ffwll.ch \
--cc=skhan@linuxfoundation.org \
--cc=spbnick@gmail.com \
--cc=tales.aparecida@gmail.com \
--cc=torvalds@linuxfoundation.org \
--cc=vignesh.raman@collabora.com \
--cc=workflows@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.