From: Randy Dunlap <rdunlap@infradead.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
workflows@vger.kernel.org, Dan Williams <djbw@kernel.org>
Subject: Re: [PATCH RFC 3/4] MAINTAINERS: add maintainer-tip.rst to X86
Date: Tue, 14 Apr 2026 17:37:33 -0700 [thread overview]
Message-ID: <81cf7a52-cfaf-4e2f-9711-a8593ee2843d@infradead.org> (raw)
In-Reply-To: <970434c647aa1e1e9a81c87b4d5fed934d4018a7.1776176108.git.mchehab+huawei@kernel.org>
On 4/14/26 7:29 AM, Mauro Carvalho Chehab wrote:
> While the maintainer's profile for tip is there, it is not
> at X86 maintainer's entry.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 620219e48f98..a85fcae5f56e 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -28560,6 +28560,7 @@ M: Ingo Molnar <mingo@redhat.com>
> M: Borislav Petkov <bp@alien8.de>
> M: Dave Hansen <dave.hansen@linux.intel.com>
> M: x86@kernel.org
> +P: Documentation/process/maintainer-tip.rst
> R: "H. Peter Anvin" <hpa@zytor.com>
> L: linux-kernel@vger.kernel.org
> S: Maintained
--
~Randy
next prev parent reply other threads:[~2026-04-15 0:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 14:29 [PATCH RFC 0/4] Auto-generate maintainer profile entries Mauro Carvalho Chehab
2026-04-14 14:29 ` [PATCH RFC 1/4] docs: maintainers_include: auto-generate maintainer profile TOC Mauro Carvalho Chehab
2026-04-15 0:45 ` Dan Williams
2026-04-14 14:29 ` [PATCH RFC 2/4] MAINTAINERS: add an entry for media maintainers profile Mauro Carvalho Chehab
2026-04-15 0:37 ` Randy Dunlap
2026-04-14 14:29 ` [PATCH RFC 3/4] MAINTAINERS: add maintainer-tip.rst to X86 Mauro Carvalho Chehab
2026-04-15 0:37 ` Randy Dunlap [this message]
2026-04-15 0:48 ` Dan Williams
2026-04-14 14:29 ` [PATCH RFC 4/4] docs: auto-generate maintainer entry profile links Mauro Carvalho Chehab
2026-04-15 0:34 ` Randy Dunlap
2026-04-15 0:59 ` Dan Williams
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=81cf7a52-cfaf-4e2f-9711-a8593ee2843d@infradead.org \
--to=rdunlap@infradead.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+huawei@kernel.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