From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Evgeny Kolmakov <randomjack94dev@gmail.com>
Cc: qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Subject: Re: [PATCH] util/filemonitor-inotify: Use QEMU_LOCK_GUARD()
Date: Mon, 29 Jun 2026 17:29:45 +0100 [thread overview]
Message-ID: <akKdebsUImUxN0I5@redhat.com> (raw)
In-Reply-To: <20260622073647.3721-1-randomjack94dev@gmail.com>
On Mon, Jun 22, 2026 at 10:36:47AM +0300, Evgeny Kolmakov wrote:
> Replace manual qemu_mutex_(un)lock() calls with
> QEMU_LOCK_GUARD() to remove 'goto cleanup' code
>
> Signed-off-by: Evgeny Kolmakov <randomjack94dev@gmail.com>
> ---
> util/filemonitor-inotify.c | 28 ++++++++--------------------
> 1 file changed, 8 insertions(+), 20 deletions(-)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
and queued..
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
prev parent reply other threads:[~2026-06-29 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 7:36 [PATCH] util/filemonitor-inotify: Use QEMU_LOCK_GUARD() Evgeny Kolmakov
2026-06-29 16:29 ` Daniel P. Berrangé [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=akKdebsUImUxN0I5@redhat.com \
--to=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=randomjack94dev@gmail.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