From: Kevin Wolf <kwolf@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: eesposit@redhat.com, qemu-block@nongnu.org, jsnow@redhat.com,
qemu-devel@nongnu.org, mreitz@redhat.com, stefanha@redhat.com,
pbonzini@redhat.com, eblake@redhat.com
Subject: Re: [PATCH 0/2] introduce QEMU_AUTO_VFREE
Date: Mon, 28 Jun 2021 12:08:36 +0200 [thread overview]
Message-ID: <YNmfpBqNnXF0Mx8x@redhat.com> (raw)
In-Reply-To: <YNMOJLtbNHh2A/99@redhat.com>
Am 23.06.2021 um 12:34 hat Kevin Wolf geschrieben:
> Am 19.06.2021 um 16:21 hat Vladimir Sementsov-Ogievskiy geschrieben:
> > Hi all!
> >
> > There is a good movement to use g_autofree macro, that helps to
> > automatically call g_free on exit from code block.
> >
> > We lack similar possibility for qemu_memalign() functions family. Let's
> > add, it seems rather simple with help of "cleanup" attribute.
> >
> > I'll update more places with a follow-up if this is accepted.
>
> Good idea. Thanks, applied to the block branch.
I'm afraid I have to unqueue this:
Failures: 040 141 161 191 249
Failed 5 of 5 iotests
Maybe semantic merge conflicts that I didn't notice while applying or
rebasing.
Kevin
next prev parent reply other threads:[~2021-06-28 10:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-19 14:21 [PATCH 0/2] introduce QEMU_AUTO_VFREE Vladimir Sementsov-Ogievskiy
2021-06-19 14:21 ` [PATCH 1/2] " Vladimir Sementsov-Ogievskiy
2021-06-19 14:21 ` [PATCH 2/2] block/commit: use QEMU_AUTO_VFREE Vladimir Sementsov-Ogievskiy
2021-06-21 13:33 ` [PATCH 0/2] introduce QEMU_AUTO_VFREE Stefan Hajnoczi
2021-06-23 10:34 ` Kevin Wolf
2021-06-28 10:08 ` Kevin Wolf [this message]
2021-06-28 11:39 ` Vladimir Sementsov-Ogievskiy
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=YNmfpBqNnXF0Mx8x@redhat.com \
--to=kwolf@redhat.com \
--cc=eblake@redhat.com \
--cc=eesposit@redhat.com \
--cc=jsnow@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@virtuozzo.com \
/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).