From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
"open list:iSCSI" <qemu-block@nongnu.org>,
Juan Quintela <quintela@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>, Peter Lieven <pl@kamp.de>,
"open list:All patches CC here" <qemu-devel@nongnu.org>,
Max Reitz <mreitz@redhat.com>,
Daniel Brodsky <dnbrdsky@gmail.com>,
Alex Williamson <alex.williamson@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
Ronnie Sahlberg <ronniesahlberg@gmail.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH v5 2/2] lockable: replaced locks with lock guard macros where appropriate
Date: Tue, 14 Apr 2020 10:16:32 +0200 [thread overview]
Message-ID: <7623740b-e5e8-d966-c991-346c1c4ccee5@redhat.com> (raw)
In-Reply-To: <87y2qyxzmf.fsf@dusky.pond.sub.org>
On 14/04/20 10:03, Markus Armbruster wrote:
> Paolo Bonzini <pbonzini@redhat.com> writes:
>
>> On 11/04/20 13:19, Daniel Brodsky wrote:
>>> Just making sure this patch didn't get lost.
>>> ping http://patchwork.ozlabs.org/patch/1266336/
>>
>> The patch looks good, but it will be included in QEMU only after 5.0 is
>> released.
>
> Can we queue it for 5.1 right away?
>
I don't have a 5.1 queue right now, but I should have one soon. It's on
my todo list.
Paolo
next prev parent reply other threads:[~2020-04-14 8:17 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
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 [this message]
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=7623740b-e5e8-d966-c991-346c1c4ccee5@redhat.com \
--to=pbonzini@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=pl@kamp.de \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--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 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).