From: Randy Dunlap <rdunlap@infradead.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
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: Wed, 13 Aug 2025 18:58:12 -0700 [thread overview]
Message-ID: <98ed6868-8030-4d10-b66d-c7e3d42886f8@infradead.org> (raw)
In-Reply-To: <20250814012046.21235-1-bagasdotme@gmail.com>
Hi,
For both patches:
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
but I have a process question, I suppose.
Why send this patch series to the workflows mailing list?
(This is not the first occasion of this happening [by other people]).
Thanks.
On 8/13/25 6:20 PM, Bagas Sanjaya wrote:
> Hi,
>
> Just a little formatting cleanup for ktap docs (actually only bullet list
> items fix in [2/2]; the first patch is trivial spelling fix).
>
> Enjoy!
>
> Bagas Sanjaya (2):
> Documentation: ktap: Correct "its" spelling
> Documentation: ktap: Separate first bullet list items
>
> Documentation/dev-tools/ktap.rst | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
>
> base-commit: 0bbc2548ea85e6bda835a08c6d47d46435945cda
--
~Randy
next prev parent reply other threads:[~2025-08-14 1:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 1:20 [PATCH 0/2] Documentation: ktap: formatting cleanup 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 ` Randy Dunlap [this message]
2025-08-14 6:39 ` [PATCH 0/2] Documentation: ktap: formatting cleanup Bagas Sanjaya
2025-08-14 15:55 ` Randy Dunlap
2025-08-14 22:55 ` Bagas Sanjaya
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=98ed6868-8030-4d10-b66d-c7e3d42886f8@infradead.org \
--to=rdunlap@infradead.org \
--cc=Tim.Bird@sony.com \
--cc=bagasdotme@gmail.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=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;
as well as URLs for NNTP newsgroup(s).