From: no-reply@patchew.org
To: wsa+renesas@sang-engineering.com
Cc: famz@redhat.com, qemu-devel@nongnu.org,
linux-renesas-soc@vger.kernel.org, f4bug@amsat.org
Subject: Re: [Qemu-devel] [PATCH v2 0/3] nvram: at24c: fix problems related to "rom-size"
Date: Mon, 19 Mar 2018 14:52:57 -0700 (PDT) [thread overview]
Message-ID: <152149637617.147.13144022271990330634@71c20359a636> (raw)
In-Reply-To: <20180319213101.6100-1-wsa+renesas@sang-engineering.com>
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20180319213101.6100-1-wsa+renesas@sang-engineering.com
Subject: [Qemu-devel] [PATCH v2 0/3] nvram: at24c: fix problems related to "rom-size"
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
total=$(git log --oneline $BASE.. | wc -l)
failed=0
git config --local diff.renamelimit 0
git config --local diff.renames True
git config --local diff.algorithm histogram
commits="$(git log --format=%H --reverse $BASE..)"
for c in $commits; do
echo "Checking PATCH $n/$total: $(git log -n 1 --format=%s $c)..."
if ! git show $c --format=email | ./scripts/checkpatch.pl --mailback -; then
failed=1
echo
fi
n=$((n+1))
done
exit $failed
=== TEST SCRIPT END ===
Updating 3c8cf5a9c21ff8782164d1def7f44bd888713384
From https://github.com/patchew-project/qemu
* [new tag] patchew/20180319213101.6100-1-wsa+renesas@sang-engineering.com -> patchew/20180319213101.6100-1-wsa+renesas@sang-engineering.com
Switched to a new branch 'test'
002d73a8fa nvram: at24c: use standard error reporting
6c4df3f9e8 nvram: at24c: use a sane default for "rom-size"
22640ea981 nvram: at24c: prevent segfault by checking "rom-size"
=== OUTPUT BEGIN ===
Checking PATCH 1/3: nvram: at24c: prevent segfault by checking "rom-size"...
Checking PATCH 2/3: nvram: at24c: use a sane default for "rom-size"...
Checking PATCH 3/3: nvram: at24c: use standard error reporting...
ERROR: Error messages should not contain newlines
#40: FILE: hw/nvram/eeprom_at24c.c:64:
+ error_report("failed to write backing file\n");
ERROR: Error messages should not contain newlines
#49: FILE: hw/nvram/eeprom_at24c.c:125:
+ error_report("rom-size not allowed to be 0\n");
ERROR: Error messages should not contain newlines
#58: FILE: hw/nvram/eeprom_at24c.c:135:
+ error_report("Backing file size %lu != %u\n",
ERROR: Error messages should not contain newlines
#68: FILE: hw/nvram/eeprom_at24c.c:143:
+ error_report("Backing file incorrect permission\n");
ERROR: Error messages should not contain newlines
#78: FILE: hw/nvram/eeprom_at24c.c:165:
+ error_report("Failed initial sync with backing file\n");
total: 5 errors, 0 warnings, 59 lines checked
Your patch 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
---
Email generated automatically by Patchew [http://patchew.org/].
Please send your feedback to patchew-devel@freelists.org
prev parent reply other threads:[~2018-03-19 21:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 21:30 [Qemu-devel] [PATCH v2 0/3] nvram: at24c: fix problems related to "rom-size" Wolfram Sang
2018-03-19 21:30 ` [Qemu-devel] [PATCH v2 1/3] nvram: at24c: prevent segfault by checking "rom-size" Wolfram Sang
2018-03-20 0:48 ` Philippe Mathieu-Daudé
2018-03-20 11:07 ` Wolfram Sang
2018-03-19 21:31 ` [Qemu-devel] [PATCH v2 2/3] nvram: at24c: use a sane default for "rom-size" Wolfram Sang
2018-03-20 0:45 ` Philippe Mathieu-Daudé
2018-03-19 21:31 ` [Qemu-devel] [PATCH v2 3/3] nvram: at24c: use standard error reporting Wolfram Sang
2018-03-19 21:51 ` Eric Blake
2018-03-19 22:07 ` Wolfram Sang
2018-03-20 0:49 ` Philippe Mathieu-Daudé
2018-03-19 21:52 ` 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=152149637617.147.13144022271990330634@71c20359a636 \
--to=no-reply@patchew.org \
--cc=f4bug@amsat.org \
--cc=famz@redhat.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=wsa+renesas@sang-engineering.com \
/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).