From: Roman Penyaev <rpenyaev@suse.de>
To: hev <r@hev.cc>
Cc: linux-fsdevel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Jason Baron <jbaron@akamai.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests: add epoll selftests
Date: Wed, 09 Oct 2019 18:26:42 +0200 [thread overview]
Message-ID: <05a68675068aefd836751e9ef3ef5ef8@suse.de> (raw)
In-Reply-To: <20191009121518.4027-1-r@hev.cc>
On 2019-10-09 14:15, hev wrote:
> From: Heiher <r@hev.cc>
>
> This adds the promised selftest for epoll. It will verify the wakeups
> of epoll. Including leaf and nested mode, epoll_wait() and poll() and
> multi-threads.
Nice! The only thing I doubt this suite should be a part of
filesystems/,
maybe one level up, i.e. selftests/epoll?
Reviewed-by: Roman Penyaev <rpenyaev@suse.de>
--
Roman
prev parent reply other threads:[~2019-10-09 16:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 12:15 [PATCH] selftests: add epoll selftests hev
2019-10-09 16:26 ` Roman Penyaev [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 \
--in-reply-to=05a68675068aefd836751e9ef3ef5ef8@suse.de \
--to=rpenyaev@suse.de \
--cc=akpm@linux-foundation.org \
--cc=jbaron@akamai.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=r@hev.cc \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).