From: Jonathan Corbet <corbet@lwn.net>
To: Costa Shulyupin <costa.shul@redhat.com>,
linux-doc@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>
Cc: Costa Shulyupin <costa.shul@redhat.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] docs: consolidate human interface subsystems
Date: Fri, 19 May 2023 08:54:19 -0600 [thread overview]
Message-ID: <87fs7snzhg.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230502015040.329394-1-costa.shul@redhat.com>
Costa Shulyupin <costa.shul@redhat.com> writes:
> to make the page more organized as requested
>
> Signed-off-by: Costa Shulyupin <costa.shul@redhat.com>
> ---
> Changes:
> - fixed typo
> - fixed underline
>
> ---
> Documentation/subsystem-apis.rst | 17 ++++++++++++-----
> 1 file changed, 12 insertions(+), 5 deletions(-)
Applied.
Thanks,
jon
next prev parent reply other threads:[~2023-05-19 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 15:42 [PATCH v2] docs: consolidate human interface subsystems Costa Shulyupin
2023-05-01 19:26 ` Randy Dunlap
2023-05-02 1:50 ` [PATCH v3] " Costa Shulyupin
2023-05-19 14:54 ` Jonathan Corbet [this message]
2023-05-02 5:37 ` [PATCH v2] " kernel test robot
2023-05-02 14:51 ` Randy Dunlap
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=87fs7snzhg.fsf@meer.lwn.net \
--to=corbet@lwn.net \
--cc=costa.shul@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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