From: no-reply@patchew.org
To: kevinb@redhat.com
Cc: qemu-devel@nongnu.org, kevinb@redhat.com
Subject: Re: [PATCH] Handle gdb.MemoryError exception in dump-guest-memory.py
Date: Fri, 14 Feb 2020 15:34:29 -0800 (PST) [thread overview]
Message-ID: <158172326858.6932.4141565337443141392@a1bbccc8075a> (raw)
In-Reply-To: <20200214232650.35381-1-kevinb@redhat.com>
Patchew URL: https://patchew.org/QEMU/20200214232650.35381-1-kevinb@redhat.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Subject: [PATCH] Handle gdb.MemoryError exception in dump-guest-memory.py
Message-id: 20200214232650.35381-1-kevinb@redhat.com
Type: series
=== TEST SCRIPT BEGIN ===
#!/bin/bash
git rev-parse base > /dev/null || exit 0
git config --local diff.renamelimit 0
git config --local diff.renames True
git config --local diff.algorithm histogram
./scripts/checkpatch.pl --mailback base..
=== TEST SCRIPT END ===
From https://github.com/patchew-project/qemu
* [new tag] patchew/20200214232650.35381-1-kevinb@redhat.com -> patchew/20200214232650.35381-1-kevinb@redhat.com
Switched to a new branch 'test'
b41300a Handle gdb.MemoryError exception in dump-guest-memory.py
=== OUTPUT BEGIN ===
ERROR: Missing Signed-off-by: line(s)
total: 1 errors, 0 warnings, 13 lines checked
Commit b41300af0818 (Handle gdb.MemoryError exception in dump-guest-memory.py) has style problems, please review. If any of these errors
are false positives report them to the maintainer, see
CHECKPATCH in MAINTAINERS.
=== OUTPUT END ===
Test command exited with code: 1
The full log is available at
http://patchew.org/logs/20200214232650.35381-1-kevinb@redhat.com/testing.checkpatch/?type=message.
---
Email generated automatically by Patchew [https://patchew.org/].
Please send your feedback to patchew-devel@redhat.com
prev parent reply other threads:[~2020-02-14 23:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 23:26 [PATCH] Handle gdb.MemoryError exception in dump-guest-memory.py Kevin Buettner
2020-02-14 23:34 ` no-reply [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=158172326858.6932.4141565337443141392@a1bbccc8075a \
--to=no-reply@patchew.org \
--cc=kevinb@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).