From: Paolo Bonzini <pbonzini@redhat.com>
To: Michal Privoznik <mprivozn@redhat.com>, qemu-devel@nongnu.org
Cc: armbru@redhat.com, peter.maydell@linaro.org, eblake@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/2] Produce better termination message
Date: Wed, 21 Sep 2016 17:25:31 +0200 [thread overview]
Message-ID: <fe4d8221-1f66-e47f-9d9c-a00f1b0ae0b5@redhat.com> (raw)
In-Reply-To: <cover.1474456806.git.mprivozn@redhat.com>
On 21/09/2016 13:26, Michal Privoznik wrote:
> v2 of:
>
> http://lists.nongnu.org/archive/html/qemu-devel/2016-09/msg04710.html
>
> The checkpatch.pl shows the following error for 1/2:
>
> ERROR: architecture specific defines should be avoided
> #63: FILE: util/oslib-posix.c:441:
> +#if defined(__FreeBSD__)
>
> But I guess we should ignore the error, since in this case we
> want OS specific code.
Yeah, this should probably be degraded to WARN.
> diff to v1:
> - Reworked 1/2 to follow Paolo's review suggestions
> - Produce "(<unknown process>)" instead of "()" in 2/2 in case
> the PID is unknown.
>
> Michal Privoznik (2):
> util: Introduce qemu_get_pid_name
> qemu_kill_report: Report PID name too
>
> include/qemu/osdep.h | 10 ++++++++++
> util/oslib-posix.c | 37 +++++++++++++++++++++++++++++++++++++
> util/oslib-win32.c | 7 +++++++
> vl.c | 8 ++++++--
> 4 files changed, 60 insertions(+), 2 deletions(-)
>
Looks good, thanks.
Paolo
prev parent reply other threads:[~2016-09-21 15:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 11:26 [Qemu-devel] [PATCH v2 0/2] Produce better termination message Michal Privoznik
2016-09-21 11:26 ` [Qemu-devel] [PATCH v2 1/2] util: Introduce qemu_get_pid_name Michal Privoznik
2016-09-21 15:24 ` Paolo Bonzini
2016-09-21 15:37 ` Daniel P. Berrange
2016-09-21 11:26 ` [Qemu-devel] [PATCH v2 2/2] qemu_kill_report: Report PID name too Michal Privoznik
2016-09-21 12:32 ` [Qemu-devel] [PATCH v2 0/2] Produce better termination message no-reply
2016-09-21 12:32 ` no-reply
2016-09-21 15:25 ` Paolo Bonzini [this message]
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=fe4d8221-1f66-e47f-9d9c-a00f1b0ae0b5@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=mprivozn@redhat.com \
--cc=peter.maydell@linaro.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).