From: Laszlo Ersek <lersek@redhat.com>
To: drjones@redhat.com
Cc: qemu-devel@nongnu.org, famz@redhat.com,
frankja@linux.vnet.ibm.com, marcandre.lureau@redhat.com
Subject: Re: [Qemu-devel] [PATCH] dump-guest-memory: more descriptive lookup_type failure
Date: Thu, 15 Mar 2018 20:26:54 +0100 [thread overview]
Message-ID: <52342f07-325c-d252-1845-97c55ea87b8f@redhat.com> (raw)
In-Reply-To: <152103749688.51.951110294839758890@71c20359a636>
On 03/14/18 15:24, no-reply@patchew.org wrote:
> Checking PATCH 1/1: dump-guest-memory: more descriptive lookup_type failure...
> WARNING: line over 80 characters
> #34: FILE: scripts/dump-guest-memory.py:22:
> + raise gdb.GdbError("Symbols must be loaded prior to sourcing dump-guest-memory.\n"
>
> ERROR: line over 90 characters
> #35: FILE: scripts/dump-guest-memory.py:23:
> + "Symbols may be loaded by first 'attach'ing a QEMU process id or by 'load'ing a QEMU binary.")
>
> total: 1 errors, 1 warnings, 12 lines checked
The current "width" of the script is currently:
$ wc -L scripts/dump-guest-memory.py
81 scripts/dump-guest-memory.py
I think it would be good to stick with 80 chars in this patch. (While
adhering to whatever Python idioms are considered necessary -- I think
Janosch and Marc-André can help with that.)
Once that's fixed, please add my:
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
(And, I agree, this error message has been reported several times to me
as well.)
Thanks!
Laszlo
next prev parent reply other threads:[~2018-03-15 19:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 14:21 [Qemu-devel] [PATCH] dump-guest-memory: more descriptive lookup_type failure Andrew Jones
2018-03-14 14:24 ` no-reply
2018-03-15 19:26 ` Laszlo Ersek [this message]
2018-03-14 15:12 ` Janosch Frank
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=52342f07-325c-d252-1845-97c55ea87b8f@redhat.com \
--to=lersek@redhat.com \
--cc=drjones@redhat.com \
--cc=famz@redhat.com \
--cc=frankja@linux.vnet.ibm.com \
--cc=marcandre.lureau@redhat.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 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).