From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Ricardo Ribalda <ribalda@chromium.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Hans Verkuil <hans@jjverkuil.nl>,
linux-media@vger.kernel.org
Subject: Re: [PATCH v4l-utils] CONTRIBUTE: Add simple contribution instructions
Date: Fri, 6 Jun 2025 10:51:08 +0200 [thread overview]
Message-ID: <20250606105108.2578ac7b@foz.lan> (raw)
In-Reply-To: <CANiDSCtEiEe4J76tJzEv5dTNxVepTN22XCt7a6B-ncgxnVo3rA@mail.gmail.com>
Em Fri, 6 Jun 2025 10:08:58 +0200
Ricardo Ribalda <ribalda@chromium.org> escreveu:
> Hi
>
> On Fri, 6 Jun 2025 at 09:52, Mauro Carvalho Chehab
> <mchehab+huawei@kernel.org> wrote:
> >
> > Em Thu, 5 Jun 2025 16:17:00 +0300
> > Laurent Pinchart <laurent.pinchart@ideasonboard.com> escreveu:
> >
> > > On Thu, Jun 05, 2025 at 02:54:33PM +0200, Ricardo Ribalda wrote:
> > > > On Thu, 5 Jun 2025 at 14:46, Laurent Pinchart wrote:
> > > > > On Thu, Jun 05, 2025 at 12:09:57PM +0000, Ricardo Ribalda wrote:
> > > > > > In the media summit we discussed the need of a special prefix for
> > > > > > v4l-utils. This helps patchwork and media-ci.
> > > > > >
> > > > > > Create a new file with a brief introductions on how to contribute and
> > > > > > make the `v4l-utils` official.
> > > > > >
> > > > > > Signed-off-by: Ricardo Ribalda <ribalda@chromium.org>
> > > > >
> > > > > I think this is a good idea. I don't know how we'll get users to
> > > > > actually use the prefix, but documenting it is a necessary first step.
> >
> > It is a good idea, but I'd say that, if there is "v4l-utils" anywhere
> > at the patch series subject, media CI shall not change the patch
> > status. Same applies to the other userspace tools we maintain.
>
> media-CI only changes the status if the followings conditions are met:
> - There is no v4l-utils in the subject
Please check also for the other userspace tools we maintain.
> - The patch can be applied on top of media-committers
> - It does not modify any media file
>
> Only if those 3 conditions are met, we mark the patch as
> not-applicable and send an email to media-maintainers about that to
> avoid false positives.
With the addition of the names of the other userspace tools, that's
OK!
Thanks,
Mauro
prev parent reply other threads:[~2025-06-06 8:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 12:09 [PATCH v4l-utils] CONTRIBUTE: Add simple contribution instructions Ricardo Ribalda
2025-06-05 12:46 ` Laurent Pinchart
2025-06-05 12:54 ` Ricardo Ribalda
2025-06-05 13:17 ` Laurent Pinchart
2025-06-05 13:54 ` Ricardo Ribalda
2025-06-06 7:52 ` Mauro Carvalho Chehab
2025-06-06 8:08 ` Ricardo Ribalda
2025-06-06 8:51 ` Mauro Carvalho Chehab [this message]
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=20250606105108.2578ac7b@foz.lan \
--to=mchehab+huawei@kernel.org \
--cc=hans@jjverkuil.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=ribalda@chromium.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.