From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: Greg Kurz <groug@kaod.org>
Subject: [PATCH 0/8] 9pfs: more local tests
Date: Tue, 20 Oct 2020 01:17:14 +0200 [thread overview]
Message-ID: <cover.1603149434.git.qemu_oss@crudebyte.com> (raw)
Just a bunch of more test case using the 9pfs 'local' fs driver backend,
namely for these 9p requests:
* Tunlinkat, Tlcreate, Tsymlink and Tlink.
Christian Schoenebeck (8):
tests/9pfs: simplify fs_mkdir()
tests/9pfs: add local unlinkat directory test
tests/9pfs: add local Tlcreate test
tests/9pfs: add local unlinkat file test
tests/9pfs: add local Tsymlink test
tests/9pfs: add local unlinkat symlink test
tests/9pfs: add local Tlink test
tests/9pfs: add local unlinkat hard link test
tests/qtest/virtio-9p-test.c | 395 ++++++++++++++++++++++++++++++++++-
1 file changed, 390 insertions(+), 5 deletions(-)
--
2.20.1
next reply other threads:[~2020-10-19 23:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 23:17 Christian Schoenebeck [this message]
2020-10-19 23:13 ` [PATCH 2/8] tests/9pfs: add local unlinkat directory test Christian Schoenebeck
2020-10-19 23:13 ` [PATCH 1/8] tests/9pfs: simplify fs_mkdir() Christian Schoenebeck
2020-10-20 13:35 ` Greg Kurz
2020-10-20 13:43 ` Christian Schoenebeck
2020-10-20 13:59 ` Greg Kurz
2020-10-20 18:03 ` Greg Kurz
2020-10-20 18:26 ` Christian Schoenebeck
2020-10-19 23:13 ` [PATCH 8/8] tests/9pfs: add local unlinkat hard link test Christian Schoenebeck
2020-10-19 23:13 ` [PATCH 7/8] tests/9pfs: add local Tlink test Christian Schoenebeck
2020-10-20 0:01 ` Christian Schoenebeck
2020-10-19 23:13 ` [PATCH 3/8] tests/9pfs: add local Tlcreate test Christian Schoenebeck
2020-10-19 23:13 ` [PATCH 5/8] tests/9pfs: add local Tsymlink test Christian Schoenebeck
2020-10-19 23:13 ` [PATCH 4/8] tests/9pfs: add local unlinkat file test Christian Schoenebeck
2020-10-19 23:13 ` [PATCH 6/8] tests/9pfs: add local unlinkat symlink test Christian Schoenebeck
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=cover.1603149434.git.qemu_oss@crudebyte.com \
--to=qemu_oss@crudebyte.com \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.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).