From: Paolo Bonzini <pbonzini@redhat.com>
To: Greg Kurz <groug@kaod.org>
Cc: Thomas Huth <thuth@redhat.com>,
berrange@redhat.com, qemu-devel@nongnu.org, dgilbert@redhat.com
Subject: Re: [PATCH] virtfs-proxy-helper: switch from libcap to libcap-ng
Date: Fri, 29 Nov 2019 13:49:20 +0100 [thread overview]
Message-ID: <4e49ea13-fe0c-2b06-052e-474d714b88ad@redhat.com> (raw)
In-Reply-To: <20191129133241.738b70ed@bahia.w3ibm.bluemix.net>
On 29/11/19 13:32, Greg Kurz wrote:
> Nice. :)
>
> Reviewed-by: Greg Kurz <groug@kaod.org>
>
> Paolo,
>
> I can take this through my 9p tree if you want. Otherwise,
>
> Acked-by: Greg Kurz <groug@kaod.org>
Yes, please do it since it's self-contained. You'd probably also test
it better than me. :)
Paolo
next prev parent reply other threads:[~2019-11-29 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 11:16 [PATCH] virtfs-proxy-helper: switch from libcap to libcap-ng Paolo Bonzini
2019-11-29 12:09 ` Daniel P. Berrangé
2019-11-29 12:32 ` Greg Kurz
2019-11-29 12:49 ` Paolo Bonzini [this message]
2019-11-29 12:59 ` Greg Kurz
2019-12-03 10:34 ` Greg Kurz
2019-12-03 11:51 ` Paolo Bonzini
2019-11-29 14:55 ` Daniel P. Berrangé
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=4e49ea13-fe0c-2b06-052e-474d714b88ad@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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).