[Qemu-devel] [PATCH for-2.10 0/4] bsd-user: silence warnings on OpenBSD

Peter Maydell posted 4 patches 6 years, 9 months ago
Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/qemu tags/patchew/1500395194-21455-1-git-send-email-peter.maydell@linaro.org
Test FreeBSD passed
Test checkpatch failed
Test docker passed
Test s390x passed
bsd-user/bsdload.c | 25 +------------------------
bsd-user/elfload.c | 10 ++++------
bsd-user/main.c    |  7 ++++---
bsd-user/mmap.c    |  2 +-
4 files changed, 10 insertions(+), 34 deletions(-)
[Qemu-devel] [PATCH for-2.10 0/4] bsd-user: silence warnings on OpenBSD
Posted by Peter Maydell 6 years, 9 months ago
I've just managed to get an OpenBSD VM into my test set for processing
pull requests. There are a handful of minor compiler warnings in
bsd-user, which this patchset fixes, just to reduce the noise
in my logs.

thanks
-- PMM

Peter Maydell (4):
  bsd-user/mmap.c: Move __thread attribute to right place
  bsd-user/elfload.c: Fix set-but-not-used warnings
  bsd-user/bsdload.c: Remove write-only id_change variable
  bsd-user/main.c: Fix unused variable warning

 bsd-user/bsdload.c | 25 +------------------------
 bsd-user/elfload.c | 10 ++++------
 bsd-user/main.c    |  7 ++++---
 bsd-user/mmap.c    |  2 +-
 4 files changed, 10 insertions(+), 34 deletions(-)

-- 
2.7.4


Re: [Qemu-devel] [PATCH for-2.10 0/4] bsd-user: silence warnings on OpenBSD
Posted by no-reply@patchew.org 6 years, 9 months ago
Hi,

This series seems to have some coding style problems. See output below for
more information:

Subject: [Qemu-devel] [PATCH for-2.10 0/4] bsd-user: silence warnings on OpenBSD
Message-id: 1500395194-21455-1-git-send-email-peter.maydell@linaro.org
Type: series

=== 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

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
Switched to a new branch 'test'
2205391 bsd-user/main.c: Fix unused variable warning
72ca90a bsd-user/bsdload.c: Remove write-only id_change variable
8d5f872 bsd-user/elfload.c: Fix set-but-not-used warnings
684257a bsd-user/mmap.c: Move __thread attribute to right place

=== OUTPUT BEGIN ===
Checking PATCH 1/4: bsd-user/mmap.c: Move __thread attribute to right place...
Checking PATCH 2/4: bsd-user/elfload.c: Fix set-but-not-used warnings...
Checking PATCH 3/4: bsd-user/bsdload.c: Remove write-only id_change variable...
Checking PATCH 4/4: bsd-user/main.c: Fix unused variable warning...
ERROR: if this code is redundant consider removing it
#26: FILE: bsd-user/main.c:622:
+#if 0

total: 1 errors, 0 warnings, 13 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
Re: [Qemu-devel] [PATCH for-2.10 0/4] bsd-user: silence warnings on OpenBSD
Posted by Peter Maydell 6 years, 9 months ago
On 18 July 2017 at 17:26, Peter Maydell <peter.maydell@linaro.org> wrote:
> I've just managed to get an OpenBSD VM into my test set for processing
> pull requests. There are a handful of minor compiler warnings in
> bsd-user, which this patchset fixes, just to reduce the noise
> in my logs.
>
> thanks
> -- PMM
>
> Peter Maydell (4):
>   bsd-user/mmap.c: Move __thread attribute to right place
>   bsd-user/elfload.c: Fix set-but-not-used warnings
>   bsd-user/bsdload.c: Remove write-only id_change variable
>   bsd-user/main.c: Fix unused variable warning

I've applied patches 1 and 2 to master; patch 3 still awaiting
review and 4 review/reply to my response-to-review...

thanks
-- PMM