From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: "Greg Kurz" <groug@kaod.org>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH 0/5] 9pfs: introduce P9Array
Date: Thu, 14 Oct 2021 15:25:59 +0200 [thread overview]
Message-ID: <2973052.dVDylayGH2@silver> (raw)
In-Reply-To: <cover.1633097129.git.qemu_oss@crudebyte.com>
On Freitag, 1. Oktober 2021 16:25:22 CEST Christian Schoenebeck wrote:
> This is simply a refactored follow-up of the following previous series
> ("introduce QArray"):
> https://lists.gnu.org/archive/html/qemu-devel/2021-08/msg04530.html
>
> There was no consensus about a project wide "QArray" shared utility code,
> nor does there seem to be a need for a project wide code, so let's just
> refactor QArray -> P9Array and make it a 9P local type for now:
> https://lists.gnu.org/archive/html/qemu-devel/2021-09/msg07743.html
>
> Changes QArray v3 -> P9Array v1:
>
> * Moved header file, i.e. include/qemu/qarray.h -> fsdev/p9array.h
>
> * Refactored *QArray* -> *P9Array*
>
> * Refactored P9ARRAY_CREATE -> P9ARRAY_NEW and
> p9array_create_* -> p9array_new_* accordingly
>
> * Refactored DECLARE_P9ARRAY_TYPE -> P9ARRAY_DECLARE_TYPE
>
> * Refactored DEFINE_P9ARRAY_TYPE -> P9ARRAY_DEFINE_TYPE
>
> [No behaviour changes whatsoever]
>
> Christian Schoenebeck (5):
> 9pfs: introduce P9Array
> fsdev/p9array.h: check scalar type in P9ARRAY_NEW()
> 9pfs: make V9fsString usable via P9Array API
> 9pfs: make V9fsPath usable via P9Array API
> 9pfs: use P9Array in v9fs_walk()
>
> fsdev/9p-marshal.c | 2 +
> fsdev/9p-marshal.h | 3 +
> fsdev/file-op-9p.h | 2 +
> fsdev/p9array.h | 160 +++++++++++++++++++++++++++++++++++++++++++++
> hw/9pfs/9p.c | 19 ++----
> 5 files changed, 174 insertions(+), 12 deletions(-)
> create mode 100644 fsdev/p9array.h
Queued on 9p.next:
https://github.com/cschoenebeck/qemu/commits/9p.next
Thanks!
Best regards,
Christian Schoenebeck
Best regards,
Christian Schoenebeck
prev parent reply other threads:[~2021-10-14 13:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 14:25 [PATCH 0/5] 9pfs: introduce P9Array Christian Schoenebeck
2021-10-01 14:26 ` [PATCH 1/5] " Christian Schoenebeck
2021-10-01 15:16 ` Daniel P. Berrangé
2021-10-01 15:27 ` Christian Schoenebeck
2021-10-01 14:27 ` [PATCH 2/5] fsdev/p9array.h: check scalar type in P9ARRAY_NEW() Christian Schoenebeck
2021-10-01 14:27 ` [PATCH 3/5] 9pfs: make V9fsString usable via P9Array API Christian Schoenebeck
2021-10-01 14:27 ` [PATCH 4/5] 9pfs: make V9fsPath " Christian Schoenebeck
2021-10-01 14:27 ` [PATCH 5/5] 9pfs: use P9Array in v9fs_walk() Christian Schoenebeck
2021-10-14 13:25 ` Christian Schoenebeck [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=2973052.dVDylayGH2@silver \
--to=qemu_oss@crudebyte.com \
--cc=berrange@redhat.com \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).