From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: Greg Kurz <groug@kaod.org>
Subject: Re: [PATCH v2 0/5] tests/9pfs: Code refactoring
Date: Tue, 20 Oct 2020 19:23:19 +0200 [thread overview]
Message-ID: <2043652.ohusmZrI9R@silver> (raw)
In-Reply-To: <160320977352.266767.5622969302437522296.stgit@bahia.lan>
On Dienstag, 20. Oktober 2020 18:09:07 CEST Greg Kurz wrote:
> Some code refactoring to have a clear distinction between top level
> test functions and helper functions.
>
> v2: - use "do_" prefix instead of "do_fs_"
>
> ---
>
> Greg Kurz (5):
> tests/9pfs: Factor out do_version() helper
> tests/9pfs: Turn fs_readdir_split() into a helper
> tests/9pfs: Set alloc in fs_create_dir()
> tests/9pfs: Factor out do_attach() helper
> tests/9pfs: Turn fs_mkdir() into a helper
>
>
> tests/qtest/virtio-9p-test.c | 62
> +++++++++++++++++++++++------------------- 1 file changed, 34
> insertions(+), 28 deletions(-)
>
> --
> Greg
Queued on 9p.next:
https://github.com/cschoenebeck/qemu/commits/9p.next
I just tweaked the order of the patches to prevent intermediate compiler
errors.
Thanks!
Best regards,
Christian Schoenebeck
next prev parent reply other threads:[~2020-10-20 17:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-20 16:09 [PATCH v2 0/5] tests/9pfs: Code refactoring Greg Kurz
2020-10-20 16:09 ` [PATCH v2 1/5] tests/9pfs: Factor out do_version() helper Greg Kurz
2020-10-20 16:09 ` [PATCH v2 2/5] tests/9pfs: Turn fs_readdir_split() into a helper Greg Kurz
2020-10-20 16:09 ` [PATCH v2 3/5] tests/9pfs: Set alloc in fs_create_dir() Greg Kurz
2020-10-20 16:09 ` [PATCH v2 4/5] tests/9pfs: Factor out do_attach() helper Greg Kurz
2020-10-20 16:09 ` [PATCH v2 5/5] tests/9pfs: Turn fs_mkdir() into a helper Greg Kurz
2020-10-20 17:23 ` Christian Schoenebeck [this message]
2020-10-20 18:00 ` [PATCH v2 0/5] tests/9pfs: Code refactoring Greg Kurz
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=2043652.ohusmZrI9R@silver \
--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).