From: no-reply@patchew.org
To: laurent@vivier.eu
Cc: famz@redhat.com, qemu-devel@nongnu.org, peter.maydell@linaro.org,
rth@twiddle.net, riku.voipio@iki.fi,
glaubitz@physik.fu-berlin.de
Subject: Re: [Qemu-devel] [PATCH v3 0/3] linux-user: some patches for hppa
Date: Thu, 26 Jan 2017 00:14:05 -0800 (PST) [thread overview]
Message-ID: <148541844416.27.6723497308743114062@eba24e3a0d7f> (raw)
In-Reply-To: <20170126080449.28255-1-laurent@vivier.eu>
Hi,
Your series seems to have some coding style problems. See output below for
more information:
Type: series
Subject: [Qemu-devel] [PATCH v3 0/3] linux-user: some patches for hppa
Message-id: 20170126080449.28255-1-laurent@vivier.eu
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
total=$(git log --oneline $BASE.. | wc -l)
failed=0
# Useful git options
git config --local diff.renamelimit 0
git config --local diff.renames True
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/20170126080449.28255-1-laurent@vivier.eu -> patchew/20170126080449.28255-1-laurent@vivier.eu
Switched to a new branch 'test'
c3c9013 linux-user: define correct UTS machine name for hppa
7b0be21 linux-user: fix "apt-get update" on linux-user hppa
ab50177 linux-user: add hppa magic numbers in qemu-binfmt-conf.sh
=== OUTPUT BEGIN ===
Checking PATCH 1/3: linux-user: add hppa magic numbers in qemu-binfmt-conf.sh...
ERROR: line over 90 characters
#34: FILE: scripts/qemu-binfmt-conf.sh:95:
+hppa_magic='\x7f\x45\x4c\x46\x01\x02\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\x0f'
ERROR: line over 90 characters
#35: FILE: scripts/qemu-binfmt-conf.sh:96:
+hppa_mask='\xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff'
total: 2 errors, 0 warnings, 22 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.
Checking PATCH 2/3: linux-user: fix "apt-get update" on linux-user hppa...
Checking PATCH 3/3: linux-user: define correct UTS machine name for hppa...
=== 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:[~2017-01-26 8:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 8:04 [Qemu-devel] [PATCH v3 0/3] linux-user: some patches for hppa Laurent Vivier
2017-01-26 8:04 ` [Qemu-devel] [PATCH v3 1/3] linux-user: add hppa magic numbers in qemu-binfmt-conf.sh Laurent Vivier
2017-01-26 8:04 ` [Qemu-devel] [PATCH v3 2/3] linux-user: fix "apt-get update" on linux-user hppa Laurent Vivier
2017-01-26 8:04 ` [Qemu-devel] [PATCH v3 3/3] linux-user: define correct UTS machine name for hppa Laurent Vivier
2017-01-26 8:14 ` 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=148541844416.27.6723497308743114062@eba24e3a0d7f \
--to=no-reply@patchew.org \
--cc=famz@redhat.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=laurent@vivier.eu \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
--cc=rth@twiddle.net \
/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).