From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35140) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cyuiF-0002Lf-0Z for qemu-devel@nongnu.org; Fri, 14 Apr 2017 02:28:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cyuiE-00075r-19 for qemu-devel@nongnu.org; Fri, 14 Apr 2017 02:28:07 -0400 Date: Fri, 14 Apr 2017 14:27:57 +0800 From: Fam Zheng Message-ID: <20170414062757.GB12191@lemon> References: <20170207235757.2026-1-mreitz@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PATCH] progress: Show current progress on SIGINFO List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Max Reitz Cc: qemu-block@nongnu.org, Kevin Wolf , qemu-devel@nongnu.org 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 > > --- > > 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