From: Fam Zheng <famz@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: qemu-block@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] progress: Show current progress on SIGINFO
Date: Fri, 14 Apr 2017 14:27:57 +0800 [thread overview]
Message-ID: <20170414062757.GB12191@lemon> (raw)
In-Reply-To: <efaef6ef-a1a5-a767-72a6-8c93ba0d9dd1@redhat.com>
On Thu, 04/13 22:38, Max Reitz wrote:
> On 08.02.2017 00:57, Max Reitz wrote:
> > Currently we only print progress information on retrieval of SIGUSR1.
> > Some systems have a dedicated SIGINFO for this, however, so it should be
> > handled appropriately if it is available.
> >
> > Buglink: https://bugs.launchpad.net/qemu/+bug/1662468
> > Signed-off-by: Max Reitz <mreitz@redhat.com>
> > ---
> > Can anyone test this on a BSD system? O:-)
> > ---
> > util/qemu-progress.c | 3 +++
> > qemu-img.texi | 3 ++-
> > 2 files changed, 5 insertions(+), 1 deletion(-)
>
> Ping
>
> (If nobody replies in the next month or so, I'm just going to merge
> this, as util/qemu-progress.c doesn't have a maintainer.)
qemu-img.c is the sole user, so it implicitly belongs to the block maintainers,
I assume.
Actually, why not add this file under block layer section of MAINTAINERS?
Fam
next prev parent reply other threads:[~2017-04-14 6:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 23:57 [Qemu-devel] [PATCH] progress: Show current progress on SIGINFO Max Reitz
2017-02-13 14:29 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-03-18 2:34 ` [Qemu-devel] " Max Reitz
2017-04-13 20:38 ` Max Reitz
2017-04-13 21:11 ` [Qemu-devel] [Qemu-block] " John Snow
2017-04-14 6:27 ` Fam Zheng [this message]
2017-04-28 16:48 ` [Qemu-devel] " Max Reitz
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=20170414062757.GB12191@lemon \
--to=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).