From: Xinghui Li <[email protected]>
To: Jens Axboe <[email protected]>, <[email protected]>
Cc: <[email protected]>, <[email protected]>,
Xinghui Li <[email protected]>
Subject: Re: [PATCH] io_uring: fix a typo in comment
Date: Thu, 30 Jun 2022 10:28:55 +0800 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 2022/6/29 22:46,“Jens Axboe”<[email protected]> wrote:
>
> On 6/29/22 8:43 AM, [email protected] wrote:
> > From: Xinghui Li <[email protected]>
> >
> > fix a typo in comment in io_allocate_scq_urings.
> > sane -> same.
> >
> > Signed-off-by: Xinghui Li <[email protected]>
> > ---
> > fs/io_uring.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/fs/io_uring.c b/fs/io_uring.c
> > index d3ee4fc532fa..af17adf3fa79 100644
> > --- a/fs/io_uring.c
> > +++ b/fs/io_uring.c
> > @@ -12284,7 +12284,7 @@ static __cold int io_allocate_scq_urings(struct io_ring_ctx *ctx,
> > struct io_rings *rings;
> > size_t size, sq_array_offset;
> >
> > - /* make sure these are sane, as we already accounted them */
> > + /* make sure these are same, as we already accounted them */
> > ctx->sq_entries = p->sq_entries;
> > ctx->cq_entries = p->cq_entries;
> That's not really a typo, though I can see why you'd think so. It's
> trying to say that we need to ensure that the ctx entries are sane,
> as they have already been accounted. This means that if we teardown
> past this point, they need to be assigned (eg sane) so that we undo
> that accounting appropriately.
Thanks a lot for your reply and I am sorry about wasting your effort. I will try to submit some valuable patches. : - )
--
Xinghui Li
prev parent reply other threads:[~2022-06-30 2:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 14:43 [PATCH] io_uring: fix a typo in comment korantwork
2022-06-29 14:46 ` Jens Axboe
2022-06-30 2:28 ` Xinghui Li [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] \
[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