All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Alistair Francis <alistair.francis@xilinx.com>
Cc: qemu-devel@nongnu.org, alistair23@gmail.com
Subject: Re: [Qemu-devel] [PATCH v1 2/5] Convert remaining error_report() to warn_report()
Date: Mon, 14 Aug 2017 13:45:20 +0200	[thread overview]
Message-ID: <87a832cqzz.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <08f16288223244deeccbdc6e4d2fced5d379504d.1501084908.git.alistair.francis@xilinx.com> (Alistair Francis's message of "Wed, 26 Jul 2017 09:07:52 -0700")

Alistair Francis <alistair.francis@xilinx.com> writes:

> In a previous patch (3dc6f8693694a649a9c83f1e2746565b47683923) we
> converted uses of error_report("warning:"... to use warn_report()
> instead. This was to help standardise on a single method of printing
> warnings to the user.
>
> There appears to have been some cases that slipped through in patch sets
> applied around the same time, this patch catches the few remaining
> cases.
>
> All of the warnings were changed using this command:
>   find ./* -type f -exec sed -i \
>     's|error_report(".*warning[,:] |warn_report("|Ig' {} +
>
> Indentation fixed up manually afterwards.
>
> Signed-off-by: Alistair Francis <alistair.francis@xilinx.com>
> Cc: Kevin Wolf <kwolf@redhat.com>
> Cc: Max Reitz <mreitz@redhat.com>
> Cc: Christian Borntraeger <borntraeger@de.ibm.com>
> Cc: Cornelia Huck <cohuck@redhat.com>
> Cc: Alexander Graf <agraf@suse.de>
> Cc: Richard Henderson <rth@twiddle.net>
> Cc: Stefan Hajnoczi <stefanha@redhat.com>
> ---
>
>  block/qcow2.c      | 10 +++++-----
>  target/s390x/kvm.c |  4 ++--
>  trace/control.c    |  4 ++--
>  3 files changed, 9 insertions(+), 9 deletions(-)
>
> diff --git a/block/qcow2.c b/block/qcow2.c
> index 90efa4477b..e6c6be0822 100644
> --- a/block/qcow2.c
> +++ b/block/qcow2.c
> @@ -302,11 +302,11 @@ static int qcow2_read_extensions(BlockDriverState *bs, uint64_t start_offset,
>              }
>  
>              if (!(s->autoclear_features & QCOW2_AUTOCLEAR_BITMAPS)) {
> -                error_report("WARNING: a program lacking bitmap support "
> -                             "modified this file, so all bitmaps are now "
> -                             "considered inconsistent. Some clusters may be "
> -                             "leaked, run 'qemu-img check -r' on the image "
> -                             "file to fix.");
> +                warn_report("a program lacking bitmap support "
> +                            "modified this file, so all bitmaps are now "
> +                            "considered inconsistent. Some clusters may be "
> +                            "leaked, run 'qemu-img check -r' on the image "
> +                            "file to fix.");

This message is awfully long.  What about splitting it while we're there:

                   warn_report("a program lacking bitmap support "
                               "modified this file, so all bitmaps are now "
                               "considered inconsistent");
                   error_printf("Some clusters may be "leaked, "
                                "run 'qemu-img check -r' on the image "
                                "file to fix.");

>                  if (need_update_header != NULL) {
>                      /* Updating is needed to drop invalid bitmap extension. */
>                      *need_update_header = true;
> diff --git a/target/s390x/kvm.c b/target/s390x/kvm.c
> index c4c5791d27..1084923adb 100644
> --- a/target/s390x/kvm.c
> +++ b/target/s390x/kvm.c
> @@ -222,8 +222,8 @@ static void kvm_s390_enable_cmma(void)
>      };
>  
>      if (mem_path) {
> -        error_report("Warning: CMM will not be enabled because it is not "
> -                     "compatible to hugetlbfs.");
> +        warn_report("CMM will not be enabled because it is not "
> +                    "compatible to hugetlbfs.");

Not a native speaker, but here goes anyway: "compatible with".

>          return;
>      }
>      rc = kvm_vm_ioctl(kvm_state, KVM_SET_DEVICE_ATTR, &attr);
> diff --git a/trace/control.c b/trace/control.c
> index 82d8989c4d..2769934bec 100644
> --- a/trace/control.c
> +++ b/trace/control.c
> @@ -72,8 +72,8 @@ void trace_event_register_group(TraceEvent **events)
>          if (likely(next_vcpu_id < CPU_TRACE_DSTATE_MAX_EVENTS)) {
>              events[i]->vcpu_id = next_vcpu_id++;
>          } else {
> -            error_report("WARNING: too many vcpu trace events; dropping '%s'",
> -                         events[i]->name);
> +            warn_report("too many vcpu trace events; dropping '%s'",
> +                        events[i]->name);
>          }
>      }
>      event_groups = g_renew(TraceEventGroup, event_groups, nevent_groups + 1);

The nits I picked predate your patch, so:
Reviewed-by: Markus Armbruster <armbru@redhat.com>

  parent reply	other threads:[~2017-08-14 11:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-26 16:07 [Qemu-devel] [PATCH v1 0/5] More warning reporting fixed Alistair Francis
2017-07-26 16:07 ` [Qemu-devel] [PATCH v1 1/5] hw/i386: Improve some of the warning messages Alistair Francis
2017-07-26 16:07 ` [Qemu-devel] [PATCH v1 2/5] Convert remaining error_report() to warn_report() Alistair Francis
2017-07-27  8:07   ` Cornelia Huck
2017-08-14 11:45   ` Markus Armbruster [this message]
2017-08-14 18:35     ` Alistair Francis
2017-07-26 16:07 ` [Qemu-devel] [PATCH v1 3/5] Convert single line fprintf() " Alistair Francis
2017-07-26 16:07 ` [Qemu-devel] [PATCH v1 4/5] Convert multi-line " Alistair Francis
2017-07-27  8:13   ` Cornelia Huck
2017-08-15  6:42   ` Markus Armbruster
2017-07-26 16:07 ` [Qemu-devel] [PATCH v1 5/5] Convert single line " Alistair Francis
2017-07-26 16:28   ` Daniel P. Berrange
2017-07-26 16:33     ` Alistair Francis
2017-07-26 16:36       ` Daniel P. Berrange
2017-07-26 16:39         ` Alistair Francis

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=87a832cqzz.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=alistair.francis@xilinx.com \
    --cc=alistair23@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.