Maintainer workflows discussions
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
	workflows@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>
Subject: [PATCH v3 01/12] MAINTAINERS: add an entry for media maintainers profile
Date: Mon, 27 Apr 2026 15:00:01 +0200	[thread overview]
Message-ID: <34aaa9258c783a05528fbad2beba69e070c3caad.1777294623.git.mchehab+huawei@kernel.org> (raw)
In-Reply-To: <cover.1777294623.git.mchehab+huawei@kernel.org>

The media subsystem has a maintainers entry profile, but its entry
is missing at MAINTAINERS.

Add it.

Acked-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Message-ID: <5af4aa6a716228eea4d59dc26b97d642e1e7d419.1776176108.git.mchehab+huawei@kernel.org>
---
 MAINTAINERS | 1 +
 1 file changed, 1 insertion(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 2fb1c75afd16..f52ec50f6d10 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -16223,6 +16223,7 @@ P:	Documentation/driver-api/media/maintainer-entry-profile.rst
 W:	https://linuxtv.org
 Q:	https://patchwork.linuxtv.org/project/linux-media/list/
 T:	git git://linuxtv.org/media.git
+P:	Documentation/driver-api/media/maintainer-entry-profile.rst
 F:	Documentation/admin-guide/media/
 F:	Documentation/devicetree/bindings/media/
 F:	Documentation/driver-api/media/
-- 
2.53.0


  reply	other threads:[~2026-04-27 13:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 13:00 [PATCH v3 00/12] Auto-generate maintainer profile entries Mauro Carvalho Chehab
2026-04-27 13:00 ` Mauro Carvalho Chehab [this message]
2026-04-27 13:00 ` [PATCH v3 02/12] MAINTAINERS: add maintainer-tip.rst to X86 Mauro Carvalho Chehab
2026-04-27 13:00 ` [PATCH v3 03/12] docs: maintainers: add SPDX license to the file Mauro Carvalho Chehab
2026-04-27 13:00 ` [PATCH v3 04/12] docs: maintainers_include: auto-generate maintainer profile TOC Mauro Carvalho Chehab
2026-04-27 13:00 ` [PATCH v3 05/12] docs: auto-generate maintainer entry profile links Mauro Carvalho Chehab
2026-04-27 13:00 ` [PATCH v3 06/12] docs: maintainers_include: use a better title for profiles Mauro Carvalho Chehab
2026-04-27 13:00 ` [PATCH v3 07/12] docs: maintainers_include: add external profile URLs Mauro Carvalho Chehab
2026-04-27 13:00 ` [PATCH v3 08/12] docs: maintainers_include: preserve names for files under process/ Mauro Carvalho Chehab
2026-04-27 13:00 ` [PATCH v3 09/12] docs: maintainers_include: Only show main entry for profiles Mauro Carvalho Chehab
2026-04-27 13:00 ` [PATCH v3 10/12] docs: maintainers_include: improve its output Mauro Carvalho Chehab
2026-04-27 13:00 ` [PATCH v3 11/12] docs: maintainers_include: fix support for O=dir Mauro Carvalho Chehab
2026-04-27 13:00 ` [PATCH v3 12/12] docs: maintainers_include: parse MAINTAINERS just once Mauro Carvalho Chehab
2026-04-27 13:05 ` [PATCH v3 00/12] Auto-generate maintainer profile entries 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=34aaa9258c783a05528fbad2beba69e070c3caad.1777294623.git.mchehab+huawei@kernel.org \
    --to=mchehab+huawei@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=rdunlap@infradead.org \
    --cc=workflows@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