linux-kernel - Re: [PATCH] media: add a subsystem profile documentation

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] [day] [month] [year] [list]

Message-ID: <20210322084018.6029c292@coco.lan>
Date:   Mon, 22 Mar 2021 08:40:18 +0100
From:   Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
To:     Jonathan Corbet <corbet@....net>
Cc:     Linux Media Mailing List <linux-media@...r.kernel.org>,
        linuxarm@...wei.com, mauro.chehab@...wei.com,
        Lukas Bulwahn <lukas.bulwahn@...il.com>,
        Mauro Carvalho Chehab <mchehab@...nel.org>,
        Randy Dunlap <rdunlap@...radead.org>,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] media: add a subsystem profile documentation

Em Mon, 08 Mar 2021 16:53:16 -0700
Jonathan Corbet <corbet@....net> escreveu:

> Mauro Carvalho Chehab <mchehab+huawei@...nel.org> writes:
> 
> > Document the basic policies of the media subsystem profile.
> >
> > Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
> > ---
> >  Documentation/driver-api/media/index.rst      |   2 +
> >  .../media/maintainer-entry-profile.rst        | 206 ++++++++++++++++++
> >  .../maintainer/maintainer-entry-profile.rst   |   1 +
> >  3 files changed, 209 insertions(+)
> >  create mode 100644 Documentation/driver-api/media/maintainer-entry-profile.rst  
> 
> This all looks good to me; would you like me to take it or were you
> going to send it upward yourself?

I prefer merging it via the media tree, as we're planning to document
additional guidelines that drivers need to comply to to be upstreamable, 
such as using V4L2 standard ioctls instead of vendor-specific extensions
to configure parameters that are handled by V4L2, not requiring a 
closed-source daemon, etc.

> 
> Thanks,
> 
> jon



Thanks,
Mauro