linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
To: "André Almeida" <andrealmeid@collabora.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	ksummit-discuss@lists.linuxfoundation.org,
	laurent.pinchart@ideasonboard.com
Subject: Re: [PATCH v2] media: add a subsystem profile documentation
Date: Wed, 18 Sep 2019 11:11:53 -0300	[thread overview]
Message-ID: <20190918111153.6f52c651@coco.lan> (raw)
In-Reply-To: <1e479f17-dbc8-b44d-bd1e-4229a6dbf151@collabora.com>

Em Wed, 18 Sep 2019 11:07:16 -0300
André Almeida <andrealmeid@collabora.com> escreveu:

> Hello Mauro,
> 
> On 9/18/19 10:59 AM, Mauro Carvalho Chehab wrote:
> > Document the basic policies of the media subsystem profile.
> > 
> > Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
> > ---
> >  Documentation/media/index.rst                 |   1 +
> >  .../media/maintainer-entry-profile.rst        | 157 ++++++++++++++++++
> >  MAINTAINERS                                   |   1 +
> >  3 files changed, 159 insertions(+)
> >  create mode 100644 Documentation/media/maintainer-entry-profile.rst
> > 
> > diff --git a/Documentation/media/index.rst b/Documentation/media/index.rst
> > index 0301c25ff887..ac94685b822a 100644
> > --- a/Documentation/media/index.rst
> > +++ b/Documentation/media/index.rst
> > @@ -12,6 +12,7 @@ Linux Media Subsystem Documentation
> >  .. toctree::
> >     :maxdepth: 2
> >  
> > +   maintainer-entry-profile
> >     media_uapi
> >     media_kapi
> >     dvb-drivers/index
> > diff --git a/Documentation/media/maintainer-entry-profile.rst b/Documentation/media/maintainer-entry-profile.rst
> > new file mode 100644
> > index 000000000000..68d642abe2c1
> > --- /dev/null
> > +++ b/Documentation/media/maintainer-entry-profile.rst
> > @@ -0,0 +1,157 @@
> > +Media Subsystem Profile
> > +=======================
> > +
> > +Overview
> > +--------
> > +
> > +The media subsystem covers support for a variety of devices: stream
> > +capture, analog and digital TV, cameras, remote controllers, HDMI CEC
> > +and media pipeline control.
> > +
> > +It covers, mainly, the contents of those directories:
> > +
> > +  - drivers/media
> > +  - drivers/staging/media
> > +  - Documentation/media
> > +  - include/media
> > +
> > +Both media userspace and Kernel APIs are documented and should be kept in
> > +sync with the API changes. It means that all patches that add new
> > +features to the subsystem should also bring changes to the corresponding
> > +API files.
> > +
> > +Also, patches that changes the Open Firmware/Device Tree bindings should
> > +also be reviewed by the Device Tree maintainers.
> > +
> > +Due to the size and wide scope of the media subsystem, media's
> > +maintainership model is to have sub-maintainers that have a broad
> > +knowledge of an specific aspect of the subsystem. It is a
> > +sub-maintainer's task to review the patches, providing feedback to users
> > +if the patches are following the subsystem rules and are properly using
> > +the media internal and external APIs.
> > +
> > +Patches for the media subsystem should be sent to the media mailing list
> > +at linux-media@vger.kernel.org as plain text only e-mail. Emails with
> > +HTML will be automatically rejected by the mail server. It could be wise
> > +to also copy the sub-maintainer(s).
> > +
> > +Media's workflow is heavily based on Patchwork, meaning that, once a patch
> > +is submitted, it should appear at:
> > +
> > +   - https://patchwork.linuxtv.org/project/linux-media/list/
> > +
> > +If it doesn't automatically appear there after a few minutes, then
> > +probably something got wrong on your submission. Please check if the
> > +email is in plain text only and if your emailer is not mangling with
> > +whitespaces before complaining or submit it again.
> > +
> > +Sub-maintainers
> > ++++++++++++++++  
> 
> What is the motivation for using "+++" instead of "---"?

Just cosmetics.

This chapter doesn't exist at the original profile, as sub-maintainers,
co-maintainers, etc. are used only on a few subsystems. 

So, I'm adding it as a sub-chapter.

Thanks,
Mauro

  reply	other threads:[~2019-09-18 14:11 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <156821693963.2951081.11214256396118531359.stgit@dwillia2-desk3.amr.corp.intel.com>
2019-09-13 16:19 ` [PATCH] media: add a subsystem profile documentation Mauro Carvalho Chehab
2019-09-17  3:35   ` single maintainer profile directory (was Re: [Ksummit-discuss] [PATCH] media: add a subsystem profile documentation) Kees Cook
2019-09-17 13:28     ` Mauro Carvalho Chehab
2019-09-17 16:33       ` Kees Cook
2019-09-18 11:23         ` [Ksummit-discuss] single maintainer profile directory (was " Mauro Carvalho Chehab
2019-09-18 17:39           ` Kees Cook
2019-09-18 18:35             ` Mauro Carvalho Chehab
2019-09-21 19:13           ` Jonathan Corbet
2019-09-21 19:45             ` Mauro Carvalho Chehab
2019-09-23 22:45             ` Kees Cook
2019-09-18 12:36   ` [Ksummit-discuss] [PATCH] media: add a subsystem profile documentation Laurent Pinchart
2019-09-18 13:57     ` Mauro Carvalho Chehab
2019-09-18 17:27       ` Laurent Pinchart
2019-09-18 18:48         ` Mauro Carvalho Chehab
2019-09-19  7:08           ` Dan Carpenter
2019-09-20  5:29             ` Joe Perches
2019-09-20 14:09               ` Daniel Vetter
2019-09-19  6:56       ` Dan Carpenter
2019-09-19  7:22         ` Geert Uytterhoeven
2019-09-19  8:49           ` Jani Nikula
2019-09-19  8:58             ` Geert Uytterhoeven
2019-09-19  9:52               ` Jani Nikula
2019-09-20 14:53           ` Laurent Pinchart
2019-09-20 14:59             ` Doug Anderson
2019-09-21  8:56               ` Jani Nikula
2019-09-23 15:58                 ` Doug Anderson
2019-09-23 16:04                   ` Jonathan Corbet
2019-09-19  9:52         ` Mauro Carvalho Chehab
2019-09-25 17:13         ` Joe Perches
2019-09-25 18:40           ` Kees Cook
2019-09-26 15:14             ` Joe Perches
2019-09-26 15:53               ` Kees Cook
2019-09-26 16:02                 ` Joe Perches
2019-09-26 16:24                   ` Kees Cook
2019-09-26 10:25           ` Geert Uytterhoeven
2019-09-18 13:59     ` [PATCH v2] " Mauro Carvalho Chehab
2019-09-18 14:07       ` André Almeida
2019-09-18 14:11         ` Mauro Carvalho Chehab [this message]
2021-02-25 13:41 Mauro Carvalho Chehab
2021-02-27  0:23 ` Randy Dunlap
2021-03-01  9:39   ` Mauro Carvalho Chehab
2021-02-27 11:13 ` Lukas Bulwahn
2021-03-01  9:40   ` Mauro Carvalho Chehab

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=20190918111153.6f52c651@coco.lan \
    --to=mchehab+samsung@kernel.org \
    --cc=andrealmeid@collabora.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.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;
as well as URLs for NNTP newsgroup(s).