public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Linux Doc Mailing List <linux-doc@vger.kernel.org>,
	linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
	workflows@vger.kernel.org, Dan Williams <djbw@kernel.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [PATCH v2 01/11] MAINTAINERS: add an entry for media maintainers profile
Date: Sun, 19 Apr 2026 21:07:30 +0200	[thread overview]
Message-ID: <20260419210730.3c9a84d1@foz.lan> (raw)
In-Reply-To: <63c25cd9-2145-40c7-b1bc-463214d5df6c@infradead.org>

On Sat, 18 Apr 2026 17:02:55 -0700
Randy Dunlap <rdunlap@infradead.org> wrote:

> On 4/16/26 11:11 PM, Mauro Carvalho Chehab wrote:
> > 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 f0b106a4dd96..620219e48f98 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -16115,6 +16115,7 @@ S:	Maintained
> >  W:	https://linuxtv.org
> >  Q:	http://patchwork.kernel.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/  
> 
> I now see 2 P: entries for MEDIA INPUT INFRASTRUCTURE
> and 2 P: entries for X86 ARCHITECTURE.
> (don't know how/why)
> 
My patches (and my tests) are based on docs-next. Perhaps some other
patch is adding them as well.

I'll rebase them on the top of -rc1 after it gets released.

Thanks,
Mauro

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2026-04-19 19:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-17  6:11 [PATCH v2 00/11] Auto-generate maintainer profile entries Mauro Carvalho Chehab
2026-04-17  6:11 ` [PATCH v2 01/11] MAINTAINERS: add an entry for media maintainers profile Mauro Carvalho Chehab
2026-04-19  0:02   ` Randy Dunlap
2026-04-19 19:07     ` Mauro Carvalho Chehab [this message]
2026-04-17  6:11 ` [PATCH v2 02/11] MAINTAINERS: add maintainer-tip.rst to X86 Mauro Carvalho Chehab
2026-04-17  6:11 ` [PATCH v2 03/11] docs: maintainers_include: auto-generate maintainer profile TOC Mauro Carvalho Chehab
2026-04-17  6:11 ` [PATCH v2 04/11] docs: auto-generate maintainer entry profile links Mauro Carvalho Chehab
2026-04-17  6:11 ` [PATCH v2 05/11] docs: maintainers_include: use a better title for profiles Mauro Carvalho Chehab
2026-04-17  6:11 ` [PATCH v2 06/11] docs: maintainers_include: add external profile URLs Mauro Carvalho Chehab
2026-04-17  6:11 ` [PATCH v2 07/11] docs: maintainers_include: preserve names for files under process/ Mauro Carvalho Chehab
2026-04-17  6:11 ` [PATCH v2 08/11] docs: maintainers_include: Only show main entry for profiles Mauro Carvalho Chehab
2026-04-17  6:11 ` [PATCH v2 09/11] docs: maintainers_include: improve its output Mauro Carvalho Chehab
2026-04-17  6:11 ` [PATCH v2 10/11] docs: maintainers_include: fix support for O=dir Mauro Carvalho Chehab
2026-04-17  6:11 ` [PATCH v2 11/11] docs: maintainers_include: parse MAINTAINERS just once Mauro Carvalho Chehab
2026-04-19  0:05 ` [PATCH v2 00/11] Auto-generate maintainer profile entries Randy Dunlap
2026-04-19 19:04   ` 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=20260419210730.3c9a84d1@foz.lan \
    --to=mchehab+huawei@kernel.org \
    --cc=corbet@lwn.net \
    --cc=djbw@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mchehab@kernel.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