From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Linux Kernel Workflows <workflows@vger.kernel.org>,
Linux Kernel Selftests <linux-kselftest@vger.kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>, David Gow <davidgow@google.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Tim Bird <Tim.Bird@sony.com>, Rae Moar <rmoar@google.com>
Subject: Re: [PATCH 0/2] Documentation: ktap: formatting cleanup
Date: Fri, 15 Aug 2025 05:55:59 +0700 [thread overview]
Message-ID: <aJ5pf-5nxHJcqzgZ@archie.me> (raw)
In-Reply-To: <e2186e21-d069-4881-8829-b698cf90d5e3@infradead.org>
On Thu, Aug 14, 2025 at 08:55:08AM -0700, Randy Dunlap wrote:
>
>
> On 8/13/25 11:39 PM, Bagas Sanjaya wrote:
> > On Wed, Aug 13, 2025 at 06:58:12PM -0700, Randy Dunlap wrote:
> >> Why send this patch series to the workflows mailing list?
> >
> > Workflows ML is listed in get_maintainer.pl output.
>
> Thank you. I didn't realize that. So in the MAINTAINERS file
> workflows ML is listed under DOCUMENTATION PROCESS and with
> these specific directories:
>
> F: Documentation/dev-tools/
> F: Documentation/maintainer/
> F: Documentation/process/
>
> so yes, you got it right. Thanks!
>
OK, thanks!
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2025-08-14 22:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 1:20 Bagas Sanjaya
2025-08-14 1:20 ` [PATCH 1/2] Documentation: ktap: Correct "its" spelling Bagas Sanjaya
2025-08-14 1:20 ` [PATCH 2/2] Documentation: ktap: Separate first bullet list items Bagas Sanjaya
2025-08-14 1:58 ` [PATCH 0/2] Documentation: ktap: formatting cleanup Randy Dunlap
2025-08-14 6:39 ` Bagas Sanjaya
2025-08-14 15:55 ` Randy Dunlap
2025-08-14 22:55 ` Bagas Sanjaya [this message]
2025-08-18 16:29 ` 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=aJ5pf-5nxHJcqzgZ@archie.me \
--to=bagasdotme@gmail.com \
--cc=Tim.Bird@sony.com \
--cc=corbet@lwn.net \
--cc=davidgow@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rmoar@google.com \
--cc=skhan@linuxfoundation.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