qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Maxim Levitsky <mlevitsk@redhat.com>
To: qemu-devel@nongnu.org
Cc: fam@euphon.net, kwolf@redhat.com, stefanha@redhat.com,
	qemu-block@nongnu.org, pl@kamp.de, tom.ty89@gmail.com,
	ronniesahlberg@gmail.com, pbonzini@redhat.com, mreitz@redhat.com
Subject: Re: [PATCH v2 0/5] SCSI: fix transfer limits for SCSI passthrough
Date: Wed, 09 Dec 2020 16:04:57 +0200	[thread overview]
Message-ID: <b0ed6a0471714b46dbf1303b420d331f0e5fb001.camel@redhat.com> (raw)
In-Reply-To: <160752262015.25926.10971176014472074579@600e7e483b3a>

On Wed, 2020-12-09 at 06:03 -0800, no-reply@patchew.org wrote:
> Patchew URL: https://patchew.org/QEMU/20201209135355.561745-1-mlevitsk@redhat.com/
> 
> 
> 
> Hi,
> 
> This series seems to have some coding style problems. See output below for
> more information:
> 
> Type: series
> Message-id: 20201209135355.561745-1-mlevitsk@redhat.com
> Subject: [PATCH v2 0/5] SCSI: fix transfer limits for SCSI passthrough
> 
> === 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 ===
> 
> Updating 3c8cf5a9c21ff8782164d1def7f44bd888713384
> From https://github.com/patchew-project/qemu
>  * [new tag]         patchew/20201209135355.561745-1-mlevitsk@redhat.com -> patchew/20201209135355.561745-1-mlevitsk@redhat.com
> Switched to a new branch 'test'
> 77c9000 block/scsi: correctly emulate the VPD block limits page
> 61f49e1 block: use blk_get_max_ioctl_transfer for SCSI passthrough
> 35c66d6 block: add max_ioctl_transfer to BlockLimits
> 08ba263 file-posix: add sg_get_max_segments that actually works with sg
> e9fd749 file-posix: split hdev_refresh_limits from raw_refresh_limits
> 
> === OUTPUT BEGIN ===
> 1/5 Checking commit e9fd7498060c (file-posix: split hdev_refresh_limits from raw_refresh_limits)
> 2/5 Checking commit 08ba263f565d (file-posix: add sg_get_max_segments that actually works with sg)
> 3/5 Checking commit 35c66d636d83 (block: add max_ioctl_transfer to BlockLimits)
> 4/5 Checking commit 61f49e1c953b (block: use blk_get_max_ioctl_transfer for SCSI passthrough)
> 5/5 Checking commit 77c9000b7c30 (block/scsi: correctly emulate the VPD block limits page)
> ERROR: braces {} are necessary for all arms of this statement
> #39: FILE: hw/scsi/scsi-generic.c:204:
> +            if (len < r->buflen)
+1 Good bot :-)

Best regards,
	Maxim Levitsky

> [...]
> 
> total: 1 errors, 0 warnings, 28 lines checked
> 
> Patch 5/5 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/20201209135355.561745-1-mlevitsk@redhat.com/testing.checkpatch/?type=message.
> ---
> Email generated automatically by Patchew [https://patchew.org/].
> Please send your feedback to patchew-devel@redhat.com




  reply	other threads:[~2020-12-09 14:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-09 13:53 [PATCH v2 0/5] SCSI: fix transfer limits for SCSI passthrough Maxim Levitsky
2020-12-09 13:53 ` [PATCH v2 1/5] file-posix: split hdev_refresh_limits from raw_refresh_limits Maxim Levitsky
2020-12-10 10:36   ` Tom Yan
2020-12-17 16:51     ` Maxim Levitsky
2020-12-09 13:53 ` [PATCH v2 2/5] file-posix: add sg_get_max_segments that actually works with sg Maxim Levitsky
2020-12-09 13:53 ` [PATCH v2 3/5] block: add max_ioctl_transfer to BlockLimits Maxim Levitsky
2020-12-09 13:53 ` [PATCH v2 4/5] block: use blk_get_max_ioctl_transfer for SCSI passthrough Maxim Levitsky
2020-12-09 13:53 ` [PATCH v2 5/5] block/scsi: correctly emulate the VPD block limits page Maxim Levitsky
2020-12-09 14:03 ` [PATCH v2 0/5] SCSI: fix transfer limits for SCSI passthrough no-reply
2020-12-09 14:04   ` Maxim Levitsky [this message]
2020-12-10  0:09   ` Paolo Bonzini
2020-12-10  9:37     ` Maxim Levitsky

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=b0ed6a0471714b46dbf1303b420d331f0e5fb001.camel@redhat.com \
    --to=mlevitsk@redhat.com \
    --cc=fam@euphon.net \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=pl@kamp.de \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=ronniesahlberg@gmail.com \
    --cc=stefanha@redhat.com \
    --cc=tom.ty89@gmail.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).