From: Kees Cook <keescook@chromium.org>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: mention documentation maintainer entry profile
Date: Wed, 19 Aug 2020 12:49:41 -0700 [thread overview]
Message-ID: <202008191248.9C653130F@keescook> (raw)
In-Reply-To: <20200815102658.12236-1-lukas.bulwahn@gmail.com>
On Sat, Aug 15, 2020 at 12:26:58PM +0200, Lukas Bulwahn wrote:
> Since commit 53b7f3aa411b ("Add a maintainer entry profile for
> documentation"), the documentation "subsystem" has a maintainer entry
> profile, and it deserves to be mentioned in MAINTAINERS with a suitable
> P: entry.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> applies cleanly on docs-next, and was checkpatch-ed.
>
> Jonathan, please pick this patch.
>
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index f520202fa1ef..8aa1369d5926 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -5178,6 +5178,7 @@ DOCUMENTATION
> M: Jonathan Corbet <corbet@lwn.net>
> L: linux-doc@vger.kernel.org
> S: Maintained
> +P: Documentation/doc-guide/maintainer-profile.rst
> T: git git://git.lwn.net/linux.git docs-next
> F: Documentation/
> F: scripts/documentation-file-ref-check
> --
> 2.17.1
Oh excellent! I missed this file going in originally; I need to get
similar done for seccomp, etc.
Reviewed-by: Kees Cook <keescook@chromium.org>
--
Kees Cook
next prev parent reply other threads:[~2020-08-19 19:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-15 10:26 [PATCH] MAINTAINERS: mention documentation maintainer entry profile Lukas Bulwahn
2020-08-19 19:49 ` Kees Cook [this message]
2020-08-24 22:03 ` Jonathan Corbet
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=202008191248.9C653130F@keescook \
--to=keescook@chromium.org \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
/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