From: Juan Quintela <quintela@redhat.com>
To: dnbrdsky@gmail.com
Cc: Kevin Wolf <kwolf@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
"open list:iSCSI" <qemu-block@nongnu.org>,
stefanha@gmail.com, Peter Lieven <pl@kamp.de>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Ronnie Sahlberg <ronniesahlberg@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH v5 2/2] lockable: replaced locks with lock guard macros where appropriate
Date: Mon, 06 Apr 2020 09:34:31 +0200 [thread overview]
Message-ID: <875zedm5iw.fsf@secure.laptop> (raw)
In-Reply-To: <20200404042108.389635-3-dnbrdsky@gmail.com> (dnbrdsky@gmail.com's message of "Fri, 3 Apr 2020 21:21:08 -0700")
dnbrdsky@gmail.com wrote:
> From: Daniel Brodsky <dnbrdsky@gmail.com>
>
> - ran regexp "qemu_mutex_lock\(.*\).*\n.*if" to find targets
> - replaced result with QEMU_LOCK_GUARD if all unlocks at function end
> - replaced result with WITH_QEMU_LOCK_GUARD if unlock not at end
>
> Signed-off-by: Daniel Brodsky <dnbrdsky@gmail.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
next prev parent reply other threads:[~2020-04-06 7:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-04 4:21 [PATCH v5 0/2] Replaced locks with lock guard macros dnbrdsky
2020-04-04 4:21 ` [PATCH v5 1/2] lockable: fix __COUNTER__ macro to be referenced properly dnbrdsky
2020-04-04 4:21 ` [PATCH v5 2/2] lockable: replaced locks with lock guard macros where appropriate dnbrdsky
2020-04-06 7:34 ` Juan Quintela [this message]
2020-04-11 11:19 ` Daniel Brodsky
2020-04-11 13:03 ` Paolo Bonzini
2020-04-14 8:03 ` Markus Armbruster
2020-04-14 8:16 ` Paolo Bonzini
2020-04-24 10:50 ` [PATCH v5 0/2] Replaced locks with lock guard macros Stefan Hajnoczi
2020-04-25 9:12 ` Paolo Bonzini
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=875zedm5iw.fsf@secure.laptop \
--to=quintela@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=dnbrdsky@gmail.com \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.com \
--cc=stefanha@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.