From: Jeff Moyer <jmoyer@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: Shenghui Wang <shhuiw@foxmail.com>,
viro@zeniv.linux.org.uk, linux-block@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] io_uring: use cpu_online() to check p->sq_thread_cpu instead of cpu_possible()
Date: Wed, 01 May 2019 11:40:57 -0400 [thread overview]
Message-ID: <x49tvee89o6.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <bcf4aa58-ec09-3d73-89f8-fdfdc3ea2896@kernel.dk> (Jens Axboe's message of "Wed, 1 May 2019 08:39:05 -0600")
Jens Axboe <axboe@kernel.dk> writes:
> Agree, I've cleaned it up, it was a bit of a mess.
LGTM, thanks!
-Jeff
next prev parent reply other threads:[~2019-05-01 15:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 7:24 [PATCH] io_uring: use cpu_online() to check p->sq_thread_cpu instead of cpu_possible() Shenghui Wang
2019-05-01 11:56 ` Jeff Moyer
2019-05-01 14:15 ` Jens Axboe
2019-05-01 14:32 ` Jeff Moyer
2019-05-01 14:39 ` Jens Axboe
2019-05-01 15:40 ` Jeff Moyer [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-05-07 8:00 Shenghui Wang
2019-05-07 14:40 ` Jens Axboe
2019-05-07 8:03 Shenghui Wang
2019-05-07 11:22 ` Jeff Moyer
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=x49tvee89o6.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=shhuiw@foxmail.com \
--cc=viro@zeniv.linux.org.uk \
/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).