All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: qemu-devel@nongnu.org
Cc: famz@redhat.com, lvivier@redhat.com, agraf@suse.de,
	mst@redhat.com, aik@ozlabs.ru, mdroth@linux.vnet.ibm.com,
	qemu-ppc@nongnu.org, abologna@redhat.com
Subject: Re: [Qemu-devel] [PATCHv3 0/7] Improve PCI IO window orgnaization for pseries
Date: Fri, 14 Oct 2016 16:41:09 +1100	[thread overview]
Message-ID: <20161014054109.GO28562@umbus> (raw)
In-Reply-To: <20161014041034.502017.26597@ex-std-node742.prod.rhcloud.com>

[-- Attachment #1: Type: text/plain, Size: 3020 bytes --]

On Thu, Oct 13, 2016 at 09:10:38PM -0700, no-reply@patchew.org wrote:
> Hi,
> 
> Your series seems to have some coding style problems. See output below for
> more information:

So.. this one is a fairly standard false positive.  checkpatch
complains about multiple statements in a macro when it's actually a
macro that's supposed to expand within a data structure initializer.

> Type: series
> Message-id: 1476316647-9433-1-git-send-email-david@gibson.dropbear.id.au
> Subject: [Qemu-devel] [PATCHv3 0/7] Improve PCI IO window orgnaization for pseries
> 
> === 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 show --no-patch --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'
> 8fa0718 spapr: Improved placement of PCI host bridges in guest memory map
> 6416268 spapr_pci: Add a 64-bit MMIO window
> 94e8f4c spapr: Adjust placement of PCI host bridge to allow > 1TiB RAM
> 692718a spapr_pci: Delegate placement of PCI host bridges to machine type
> 2b765c9 libqos: Limit spapr-pci to 32-bit MMIO for now
> 4543692 libqos: Correct error in PCI hole sizing for spapr
> 2c35727 libqos: Isolate knowledge of spapr memory map to qpci_init_spapr()
> 
> === OUTPUT BEGIN ===
> Checking PATCH 1/7: libqos: Isolate knowledge of spapr memory map to qpci_init_spapr()...
> Checking PATCH 2/7: libqos: Correct error in PCI hole sizing for spapr...
> Checking PATCH 3/7: libqos: Limit spapr-pci to 32-bit MMIO for now...
> Checking PATCH 4/7: spapr_pci: Delegate placement of PCI host bridges to machine type...
> Checking PATCH 5/7: spapr: Adjust placement of PCI host bridge to allow > 1TiB RAM...
> Checking PATCH 6/7: spapr_pci: Add a 64-bit MMIO window...
> ERROR: trailing whitespace
> #237: FILE: include/hw/ppc/spapr.h:44:
> +                          uint64_t *buid, hwaddr *pio, $
> 
> total: 1 errors, 0 warnings, 170 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.

In attempting to follow the suggestion above, I discovered that
checkpatch has no listed maintainer.  Maybe we should change that
message to "if any of these errors are false positives, then too bad,
suck it up"...

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-10-14  7:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-12 23:57 [Qemu-devel] [PATCHv3 0/7] Improve PCI IO window orgnaization for pseries David Gibson
2016-10-12 23:57 ` [Qemu-devel] [PATCHv3 1/7] libqos: Isolate knowledge of spapr memory map to qpci_init_spapr() David Gibson
2016-10-12 23:57 ` [Qemu-devel] [PATCHv3 2/7] libqos: Correct error in PCI hole sizing for spapr David Gibson
2016-10-12 23:57 ` [Qemu-devel] [PATCHv3 3/7] libqos: Limit spapr-pci to 32-bit MMIO for now David Gibson
2016-10-12 23:57 ` [Qemu-devel] [PATCHv3 4/7] spapr_pci: Delegate placement of PCI host bridges to machine type David Gibson
2016-10-13  7:33   ` Laurent Vivier
2016-10-12 23:57 ` [Qemu-devel] [PATCHv3 5/7] spapr: Adjust placement of PCI host bridge to allow > 1TiB RAM David Gibson
2016-10-13  7:35   ` Laurent Vivier
2016-10-12 23:57 ` [Qemu-devel] [PATCHv3 6/7] spapr_pci: Add a 64-bit MMIO window David Gibson
2016-10-13  8:06   ` Laurent Vivier
2016-10-12 23:57 ` [Qemu-devel] [PATCHv3 7/7] spapr: Improved placement of PCI host bridges in guest memory map David Gibson
2016-10-13  8:40   ` Laurent Vivier
2016-10-13 23:29     ` David Gibson
2016-10-14  7:25       ` Laurent Vivier
2016-10-16  1:06         ` David Gibson
2016-10-14  4:10 ` [Qemu-devel] [PATCHv3 0/7] Improve PCI IO window orgnaization for pseries no-reply
2016-10-14  5:41   ` David Gibson [this message]
2016-10-14  7:07     ` Laurent Vivier

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=20161014054109.GO28562@umbus \
    --to=david@gibson.dropbear.id.au \
    --cc=abologna@redhat.com \
    --cc=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=famz@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.