From: Gabriel Krisman Bertazi <[email protected]>
To: Ammar Faizi <[email protected]>
Cc: Jens Axboe <[email protected]>,
Pavel Begunkov <[email protected]>,
Breno Leitao <[email protected]>,
Christian Mazakas <[email protected]>,
Gilang Fachrezy <[email protected]>,
io-uring Mailing List <[email protected]>,
VNLX Kernel Department <[email protected]>,
Linux Kernel Mailing List <[email protected]>,
GNU/Weeb Mailing List <[email protected]>,
Jiahao XU <[email protected]>
Subject: Re: [PATCH liburing v1] man/io_uring_prep_splice.3: Fix description in io_uring_prep_splice() manpage
Date: Thu, 12 Jan 2023 17:47:49 -0300 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]> (Ammar Faizi's message of "Fri, 13 Jan 2023 03:34:52 +0700")
Ammar Faizi <[email protected]> writes:
> From: Ammar Faizi <[email protected]>
>
> Commit 55bbe5b71c7d missed a review from Gabriel. It was blindly copied
> from liburing.h comment with just a modification to support manpage
> formatting. Fix that.
>
> While in there, also fix the liburing.h from which that mistake comes.
>
> Cc: Jiahao XU <[email protected]>
> Suggested-by: Gabriel Krisman Bertazi <[email protected]>
> Link: https://lore.kernel.org/io-uring/[email protected]
> Fixes: 55bbe5b71c7d ("man/io_uring_prep_splice.3: Explain more about io_uring_prep_splice()")
> Fixes: d871f482d911 ("Add inline doc in the comments for io_uring_prep_splice")
> Signed-off-by: Ammar Faizi <[email protected]>
Reviewed-by: Gabriel Krisman Bertazi <[email protected]>
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2023-01-12 20:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 20:34 [PATCH liburing v1] man/io_uring_prep_splice.3: Fix description in io_uring_prep_splice() manpage Ammar Faizi
2023-01-12 20:47 ` Gabriel Krisman Bertazi [this message]
2023-01-12 23:16 ` Jens Axboe
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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