From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-15.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,INCLUDES_PATCH,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED, USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A35A2C49ED7 for ; Fri, 13 Sep 2019 16:19:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6DA142081B for ; Fri, 13 Sep 2019 16:19:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1568391569; bh=dg2bcYlz7I4jUQAumRUZkhB4FONM+pk2OvOTpt+gxJE=; h=From:To:Cc:Subject:Date:In-Reply-To:References:List-ID:From; b=mua6V3VmCev7CjXIj2SaegwwGKcTxPbn/BjYUY/JXVWVtz+68bVxu7fXXeIXvzs4l 1wJQVGhNS4zSvpKxHrUlF7zra3CdzA9bVh/ppZCcubu2oLKOZ8eKrZl4mUE5BZWL8I FU3hl9kyPviB+KN4bMgMbOSNbaHMmHfVwmuf/1s8= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387822AbfIMQT3 (ORCPT ); Fri, 13 Sep 2019 12:19:29 -0400 Received: from bombadil.infradead.org ([198.137.202.133]:56262 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387802AbfIMQT2 (ORCPT ); Fri, 13 Sep 2019 12:19:28 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20170209; h=Sender:Content-Transfer-Encoding: MIME-Version:References:In-Reply-To:Message-Id:Date:Subject:Cc:To:From: Reply-To:Content-Type:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help: List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=awYbIkISAQqRNu3/BAy47wyj42SZ4LuMhUuD0B9TR9M=; b=lls1mty74yD63no3gbz90wDs/z 8HbNSpe2XznoBpotDi1OHXazwAyR/7SLW//+75nnT3FanRiGckxvnJKzjJsxb2IgamP9gewKzjT5N e1bVi9o8N6gnIvdw1zakYsBky+kdCwyH6f9W/BeX7sNFehpDyN2oWcUHirWkRO9WXwUI0MNJOJJlI Tm1v1AYDbKkfNxgXcVuaehZU5ubz7fNCbvTFiM4ijApRg51Bezf6h6ew3DCQKHmRZypj6Wz22R1ZT jEfpvaMQyRVHMAW0v2599LJEESvsxFRULuvg8nI42j4wbaaFFaBIlC5rRlvEOKaR75OLKtUAW/z6r Y0yLQ+bw==; Received: from 177.96.232.144.dynamic.adsl.gvt.net.br ([177.96.232.144] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtpsa (Exim 4.92.2 #3 (Red Hat Linux)) id 1i8oIC-0000T2-4U; Fri, 13 Sep 2019 16:19:28 +0000 Received: from mchehab by bombadil.infradead.org with local (Exim 4.92.2) (envelope-from ) id 1i8oI9-0000ZY-TP; Fri, 13 Sep 2019 13:19:25 -0300 From: Mauro Carvalho Chehab To: Linux Media Mailing List Cc: Mauro Carvalho Chehab , Mauro Carvalho Chehab , Dan Williams , ksummit-discuss@lists.linuxfoundation.org Subject: [PATCH] media: add a subsystem profile documentation Date: Fri, 13 Sep 2019 13:19:21 -0300 Message-Id: <434c05bddd2b364e607e565227487910a8dd9793.1568391461.git.mchehab+samsung@kernel.org> X-Mailer: git-send-email 2.21.0 In-Reply-To: <156821693963.2951081.11214256396118531359.stgit@dwillia2-desk3.amr.corp.intel.com> References: <156821693963.2951081.11214256396118531359.stgit@dwillia2-desk3.amr.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-media-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-media@vger.kernel.org Document the basic policies of the media subsystem profile. Signed-off-by: Mauro Carvalho Chehab --- That's basically a modified version of: https://patchwork.linuxtv.org/patch/52999/ Applied to the new template Documentation/media/index.rst | 1 + .../media/maintainer-entry-profile.rst | 140 ++++++++++++++++++ MAINTAINERS | 1 + 3 files changed, 142 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..81d3b0f9c36a --- /dev/null +++ b/Documentation/media/maintainer-entry-profile.rst @@ -0,0 +1,140 @@ +Media Subsystem Profile +======================= + +Overview +-------- + +The media subsystem cover 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 for device drivers that changes the Open Firmware/Device +Tree bindings should 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-maintainers 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. There's no need +to copy the maintainer or 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 ++++++++++++++++ + +At the media subsystem, we have a group of senior developers that are +responsible for doing the code reviews at the drivers (called +sub-maintainers), and another senior developer responsible for the +subsystem as a hole. For core changes, whenever possible, multiple +media (sub-)maintainers do the review. + +The sub-maintainers work on specific areas of the subsystem, as +described below: + +Digital TV: + Sean Young + +HDMI CEC: + Hans Verkuil + +Media controller drivers: + Laurent Pinchart + +Remote Controllers: + Sean Young + +Sensor drivers: + Sakari Ailus + +V4L2 drivers: + Hans Verkuil + +Submit Checklist Addendum +------------------------- + +There is a set of compliance tools at https://git.linuxtv.org/v4l-utils.git/ +that should be used in order to check if the drivers are properly +implementing the media APIs. + +Those tests need to be passed before the patches go upstream. + +Also, please notice that we build the Kernel with:: + + make CF=-D__CHECK_ENDIAN__ CONFIG_DEBUG_SECTION_MISMATCH=y C=1 W=1 CHECK=check_script + +Where the check script is:: + + #!/bin/bash + /devel/smatch/smatch -p=kernel $@ >&2 + /devel/sparse/sparse $@ >&2 + +Be sure to not introduce new warnings on your patches. + +Key Cycle Dates +--------------- + +New submissions can be sent at any time, but if they intend to hit the +next merge window they should be sent before -rc5, and ideally stabilized +in the linux-media branch by -rc6. + +Coding Style Addendum +--------------------- + +Media development uses checkpatch on strict mode to verify the code style, e. g.:: + + $ ./script/checkpatch.pl --strict + +Review Cadence +-------------- + +Provided that your patch is at https://patchwork.linuxtv.org, it should +be sooner or later handled, so you don't need to re-submit a patch. + +Except for bug fixes, we don't usually add new patches to the development +tree between -rc6 and the next -rc1. + +Please notice that the media subsystem is a high traffic one, so it +could take a while for us to be able to review your patches. Feel free +to ping if you don't get a feedback on a couple of weeks or to ask +other developers to publicly add Reviewed-by and, more importantly, +Tested-by tags. + +Please notice that we expect a detailed description for Tested-by, +identifying what boards were used at the test and what it was tested. + +Style Cleanup Patches +--------------------- + +Style-cleanups are welcome when they come together with other changes +at the files where the style changes will affect. + +We may accept pure standalone style-cleanups, but they should be grouped +per directory. So, for example, if you're doing a cleanup at drivers +under drivers/media, please send a single patch for all drivers under +drivers/media/pci, another one for drivers/media/usb and so on. diff --git a/MAINTAINERS b/MAINTAINERS index 7c62b45201d7..e7f44ec05a42 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -10077,6 +10077,7 @@ W: https://linuxtv.org Q: http://patchwork.kernel.org/project/linux-media/list/ T: git git://linuxtv.org/media_tree.git S: Maintained +P: Documentation/media/maintainer-entry-profile.rst F: Documentation/devicetree/bindings/media/ F: Documentation/media/ F: drivers/media/ -- 2.21.0