From: Greg Kurz <groug@kaod.org>
To: no-reply@patchew.org
Cc: anthony.perard@citrix.com, sstabellini@kernel.org,
qemu_oss@crudebyte.com, qemu-devel@nongnu.org, paul@xen.org
Subject: Re: [PATCH 0/2] revert 9pfs reply truncation, wait for free room to reply
Date: Wed, 20 May 2020 15:42:36 +0200 [thread overview]
Message-ID: <20200520154236.3edf3cbc@bahia.lan> (raw)
In-Reply-To: <158996146074.24632.17962896571801369435@45ef0f9c86ae>
On Wed, 20 May 2020 00:57:42 -0700 (PDT)
no-reply@patchew.org wrote:
> Patchew URL: https://patchew.org/QEMU/alpine.DEB.2.21.2005191651130.27502@sstabellini-ThinkPad-T480s/
>
>
>
> Hi,
>
> This series seems to have some coding style problems. See output below for
> more information:
>
> Message-id: alpine.DEB.2.21.2005191651130.27502@sstabellini-ThinkPad-T480s
> Subject: [PATCH 0/2] revert 9pfs reply truncation, wait for free room to reply
> Type: series
>
> === 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
> Switched to a new branch 'test'
> 1fcf375 xen/9pfs: yield when there isn't enough room on the ring
> 8e197ec Revert "9p: init_in_iov_from_pdu can truncate the size"
>
> === OUTPUT BEGIN ===
> 1/2 Checking commit 8e197ec8340d (Revert "9p: init_in_iov_from_pdu can truncate the size")
> 2/2 Checking commit 1fcf3751db74 (xen/9pfs: yield when there isn't enough room on the ring)
> ERROR: memory barrier without comment
> #41: FILE: hw/9pfs/xen-9p-backend.c:203:
> + smp_wmb();
>
> ERROR: memory barrier without comment
> #56: FILE: hw/9pfs/xen-9p-backend.c:213:
> + smp_wmb();
>
> ERROR: memory barrier without comment
> #68: FILE: hw/9pfs/xen-9p-backend.c:302:
> + smp_rmb();
>
Indeed some comments would definitely provide better understanding.
> total: 3 errors, 0 warnings, 50 lines checked
>
> Patch 2/2 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/alpine.DEB.2.21.2005191651130.27502@sstabellini-ThinkPad-T480s/testing.checkpatch/?type=message.
> ---
> Email generated automatically by Patchew [https://patchew.org/].
> Please send your feedback to patchew-devel@redhat.com
prev parent reply other threads:[~2020-05-20 13:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 1:47 [PATCH 0/2] revert 9pfs reply truncation, wait for free room to reply Stefano Stabellini
2020-05-20 1:47 ` [PATCH 1/2] Revert "9p: init_in_iov_from_pdu can truncate the size" Stefano Stabellini
2020-05-20 11:54 ` Christian Schoenebeck
2020-05-20 1:47 ` [PATCH 2/2] xen/9pfs: yield when there isn't enough room on the ring Stefano Stabellini
2020-05-20 11:23 ` Christian Schoenebeck
2020-05-20 17:35 ` Stefano Stabellini
2020-05-20 18:46 ` Stefano Stabellini
2020-05-21 11:51 ` Christian Schoenebeck
2020-05-20 7:57 ` [PATCH 0/2] revert 9pfs reply truncation, wait for free room to reply no-reply
2020-05-20 13:42 ` Greg Kurz [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=20200520154236.3edf3cbc@bahia.lan \
--to=groug@kaod.org \
--cc=anthony.perard@citrix.com \
--cc=no-reply@patchew.org \
--cc=paul@xen.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.com \
--cc=sstabellini@kernel.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 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).