From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: "Greg Kurz" <groug@kaod.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH 0/2] 9pfs: v9fs_walk() cleanup
Date: Fri, 20 Aug 2021 16:30:33 +0200 [thread overview]
Message-ID: <2485678.SSUqDfrsUB@silver> (raw)
In-Reply-To: <cover.1629208359.git.qemu_oss@crudebyte.com>
On Dienstag, 17. August 2021 15:52:39 CEST Christian Schoenebeck wrote:
> Few cleanup patches for function v9fs_walk() as discussed last month.
>
> In patch 2 array variables 'wnames' and 'pathes' are omitted because they
> contain dynamically allocated memory per array element which need to be
> freed individually before freeing the array.
>
> Christian Schoenebeck (2):
> hw/9pfs: avoid 'path' copy in v9fs_walk()
> hw/9pfs: use g_autofree in v9fs_walk() where possible
>
> hw/9pfs/9p.c | 15 +++++++--------
> 1 file changed, 7 insertions(+), 8 deletions(-)
Queued on 9p.next:
https://github.com/cschoenebeck/qemu/commits/9p.next
Thanks!
Best regards,
Christian Schoenebeck
prev parent reply other threads:[~2021-08-20 14:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 13:52 [PATCH 0/2] 9pfs: v9fs_walk() cleanup Christian Schoenebeck
2021-08-17 12:38 ` [PATCH 1/2] hw/9pfs: avoid 'path' copy in v9fs_walk() Christian Schoenebeck
2021-08-20 10:35 ` Greg Kurz
2021-08-20 12:19 ` Christian Schoenebeck
2021-08-17 13:46 ` [PATCH 2/2] hw/9pfs: use g_autofree in v9fs_walk() where possible Christian Schoenebeck
2021-08-17 14:10 ` Philippe Mathieu-Daudé
2021-08-20 10:40 ` Greg Kurz
2021-08-20 12:23 ` Christian Schoenebeck
2021-08-20 12:34 ` Greg Kurz
2021-08-20 12:49 ` Christian Schoenebeck
2021-08-20 14:30 ` 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=2485678.SSUqDfrsUB@silver \
--to=qemu_oss@crudebyte.com \
--cc=groug@kaod.org \
--cc=philmd@redhat.com \
--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).