public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: linux-media@vger.kernel.org
Subject: Changes at the main development tree
Date: Mon, 7 Oct 2024 17:31:46 +0200	[thread overview]
Message-ID: <20241007173146.6a35fa62@foz.lan> (raw)

Hi all,

We're doing several changes on our maintainership process, aiming to provide
better handling of patches. Several changes will be happening along the time.

We'll be keeping you updated about such changes.

The first phase was already implemented: In the past, we were hosting two
separate trees (media_stage and media_tree). We opted to unify them and
name it as just media.git. Such tree is at:

	git://linuxtv.org/media.git
	https://linuxtv.org/git/media.git/
	https://git.linuxtv.org/media.git/

It contains two branches:

	next - Patches for the next Kernel version
	fixes - Fix patches for the current Kernel version

The legacy trees still exist and are now updated on every couple of
minutes to be in sync with media.git. Both trees have two branches
as well (master and fixes). We don't intend to keep them forever, so
please update your remote repositories to point to media.git.

We also updated https://git.linuxtv.org/media.git/ to make the
old trees invisible. So, right now, the only visible Linux Media
tree is "media.git".

The Jenkins CI jobs are already using the new repository.

Another change that already happened is with regards to CI: we're now
using a gitlab-based CI that has been checking patches before we
merge at media.git.

There are two different test sets there:

1. test patches we intend to merge at media.git;
2. test patches sent to the mailing list.

for (2), you can now see a new column at patchwork.linuxtv.org
	with S/W/F (success/warning/failure).

And opening a patch, like:
	https://patchwork.linuxtv.org/project/linux-media/patch/20240930-cocci-opportunity-v1-45-81e137456ce0@chromium.org/

There is a check table with:

Checks

Context 			Check 		Description
============================    ============    ===========
media-ci/HTML_report 		success 	Link
media-ci/report 		success 	Link
media-ci/virtme32 		success 	Link
media-ci/virtme64 		success 	Link
media-ci/bisect 		success 	Link
media-ci/doc 			success 	Link
media-ci/build 			success 	Link
media-ci/static-upstream 	fail 		Link
media-ci/abi		 	success 	Link
media-ci/media-patchstyle 	success 	Link
media-ci/checkpatch 		fail 		Link 

Details can be obtained by clicking at the Link.

Btw, media-ci nos has support to provide feedback via e-mail to the
patch sender in case of errors.

Thanks,
Mauro

                 reply	other threads:[~2024-10-07 15:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20241007173146.6a35fa62@foz.lan \
    --to=mchehab+huawei@kernel.org \
    --cc=linux-media@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox