From: Kees Cook <kees@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Jakub Kicinski <kuba@kernel.org>,
corbet@lwn.net, workflows@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: add Documentation/dev-tools/ to workflows@
Date: Tue, 23 Jul 2024 13:08:27 -0700 [thread overview]
Message-ID: <202407231308.90B5E1A1F9@keescook> (raw)
In-Reply-To: <6f1f7e37-c5a3-4da8-9c03-6ef469ad90ac@infradead.org>
On Mon, Jul 22, 2024 at 08:24:57AM -0700, Randy Dunlap wrote:
>
>
> On 7/22/24 7:29 AM, Jakub Kicinski wrote:
> > The goal of the workloads@ mailing list was to make it easier for
>
> workflows@
> as in $Subject.
With the typo fixed, yeah, good idea:
Reviewed-by: Kees Cook <kees@kernel.org>
-Kees
>
> > maintainers who don't use lore+lei to subscribe to topics related
> > to process changes. In other words it should cover changes to Documentation
> > files which most maintainers should know about. Recent changes from Kees [1]
> > to provide guidelines on naming KUnit files did not fall under workflows@
> > since Documentation/dev-tools/ isn't covered. The patch volume for
> > dev-tools isn't huge and most of the changes are interesting. Add it.
> >
> > Link: https://lore.kernel.org/20240720165441.it.320-kees@kernel.org/ # [1]
> > Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> > ---
> > MAINTAINERS | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index ec6904cbfd1f..a85234de4fd0 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -6680,6 +6680,7 @@ DOCUMENTATION PROCESS
> > M: Jonathan Corbet <corbet@lwn.net>
> > L: workflows@vger.kernel.org
> > S: Maintained
> > +F: Documentation/dev-tools/
> > F: Documentation/maintainer/
> > F: Documentation/process/
> >
>
> --
> ~Randy
>
--
Kees Cook
prev parent reply other threads:[~2024-07-23 20:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 14:29 Jakub Kicinski
2024-07-22 15:24 ` Randy Dunlap
2024-07-23 20:08 ` Kees Cook [this message]
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=202407231308.90B5E1A1F9@keescook \
--to=kees@kernel.org \
--cc=corbet@lwn.net \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.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