From: no-reply@patchew.org
To: oro@il.ibm.com
Cc: kwolf@redhat.com, berrange@redhat.com, qemu-block@nongnu.org,
qemu-devel@nongnu.org, to.my.trociny@gmail.com, oro@il.ibm.com,
idryomov@gmail.com, dannyh@il.ibm.com
Subject: Re: [PATCH] block/rbd: Add support for rbd image encryption
Date: Mon, 21 Jun 2021 07:27:46 -0700 (PDT) [thread overview]
Message-ID: <162428566565.6049.8269036786615275036@7c66fb7bc3ab> (raw)
In-Reply-To: <20210621142103.1417408-1-oro@il.ibm.com>
Patchew URL: https://patchew.org/QEMU/20210621142103.1417408-1-oro@il.ibm.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20210621142103.1417408-1-oro@il.ibm.com
Subject: [PATCH] block/rbd: Add support for rbd image encryption
=== 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
- [tag update] patchew/20210614083800.1166166-1-richard.henderson@linaro.org -> patchew/20210614083800.1166166-1-richard.henderson@linaro.org
* [new tag] patchew/20210621142103.1417408-1-oro@il.ibm.com -> patchew/20210621142103.1417408-1-oro@il.ibm.com
Switched to a new branch 'test'
19faaee block/rbd: Add support for rbd image encryption
=== OUTPUT BEGIN ===
ERROR: "(foo**)" should be "(foo **)"
#60: FILE: block/rbd.c:374:
+ luks_opts->key_secret, (uint8_t**)passphrase, passphrase_len, errp);
total: 1 errors, 0 warnings, 601 lines checked
Commit 19faaee12b6d (block/rbd: Add support for rbd image encryption) 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/20210621142103.1417408-1-oro@il.ibm.com/testing.checkpatch/?type=message.
---
Email generated automatically by Patchew [https://patchew.org/].
Please send your feedback to patchew-devel@redhat.com
next prev parent reply other threads:[~2021-06-21 14:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 14:21 [PATCH] block/rbd: Add support for rbd image encryption Or Ozeri
2021-06-21 14:27 ` no-reply [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-27 8:30 Or Ozeri
2021-06-27 8:44 ` Or Ozeri
2021-06-27 11:00 ` Ilya Dryomov
2021-06-27 11:09 ` Or Ozeri
2021-06-27 11:24 ` Ilya Dryomov
2021-06-21 14:48 Or Ozeri
2021-06-26 10:44 ` Ilya Dryomov
2021-06-17 16:05 Or Ozeri
2021-06-19 19:44 ` Ilya Dryomov
2021-06-20 10:35 ` Ilya Dryomov
2021-06-21 8:32 ` Daniel P. Berrangé
2021-06-21 10:59 ` Ilya Dryomov
2021-06-21 11:04 ` Daniel P. Berrangé
2021-06-21 11:23 ` Ilya Dryomov
2021-06-21 11:27 ` Daniel P. Berrangé
2021-06-21 11:52 ` Ilya Dryomov
2021-06-20 12:46 ` Or Ozeri
2021-05-05 16:48 Or Ozeri
2021-05-02 7:36 Or Ozeri
2021-05-02 14:00 ` no-reply
2021-05-04 14:46 ` Daniel P. Berrangé
2021-05-05 15:32 ` Or Ozeri
2021-05-05 15:36 ` Daniel P. Berrangé
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=162428566565.6049.8269036786615275036@7c66fb7bc3ab \
--to=no-reply@patchew.org \
--cc=berrange@redhat.com \
--cc=dannyh@il.ibm.com \
--cc=idryomov@gmail.com \
--cc=kwolf@redhat.com \
--cc=oro@il.ibm.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=to.my.trociny@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).