From: Jens Axboe <[email protected]>
To: Dylan Yudaken <[email protected]>,
[email protected], [email protected]
Cc: kernel test robot <[email protected]>
Subject: Re: [PATCH for-next] io_uring: fix documentation
Date: Thu, 23 Jun 2022 07:59:38 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 6/23/22 2:21 AM, Dylan Yudaken wrote:
> The doc strings were incorrect, fix these up
>
> Reported-by: kernel test robot <[email protected]>
> Fixes: c0808632a83a ("io_uring: introduce llist helpers")
> Signed-off-by: Dylan Yudaken <[email protected]>
> ---
>
> Hi,
>
> You may want to just fold this into the original commit.
Yeah, I'm going to fold that in with the -rc4 rebase.
--
Jens Axboe
prev parent reply other threads:[~2022-06-23 13:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 8:21 [PATCH for-next] io_uring: fix documentation Dylan Yudaken
2022-06-23 13:59 ` Jens Axboe [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 \
[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