From: no-reply@patchew.org
To: brijesh.singh@amd.com
Cc: famz@redhat.com, ehabkost@redhat.com,
crosthwaite.peter@gmail.com, armbru@redhat.com, mst@redhat.com,
p.fedin@samsung.com, qemu-devel@nongnu.org,
lcapitulino@redhat.com, pbonzini@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [RFC PATCH v2 00/16] x86: Secure Encrypted Virtualization (AMD)
Date: Thu, 22 Sep 2016 08:54:14 -0700 (PDT) [thread overview]
Message-ID: <20160922155409.382041.38351@ex-std-node742.prod.rhcloud.com> (raw)
In-Reply-To: <147455590865.8519.11191009507297313736.stgit@brijesh-build-machine>
Hi,
Your series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 147455590865.8519.11191009507297313736.stgit@brijesh-build-machine
Subject: [Qemu-devel] [RFC PATCH v2 00/16] x86: Secure Encrypted Virtualization (AMD)
=== 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
From https://github.com/patchew-project/qemu
- [tag update] patchew/1474556029-24992-1-git-send-email-ehabkost@redhat.com -> patchew/1474556029-24992-1-git-send-email-ehabkost@redhat.com
Switched to a new branch 'test'
850cc25 i386: clear C-bit in SEV guest page table walk
118801a target-i386: add cpuid Fn8000_001f
0a1150c i386: set memory encryption ops for PC.BIOS and PC.RAM regions
cc8e566 sev: add DEBUG_ENCRYPT command
7a078d0 sev: add DEBUG_DECRYPT command
86d0fa9 sev: add LAUNCH_FINISH command
2fab8c2 sev: add LAUNCH_UPDATE command
1786fb6 sev: add LAUNCH_START command
0b20533 core: loader: create memory encryption context before copying data
9d4475b hmp: display memory encryption support in 'info kvm'
a3a62fd sev: add Secure Encrypted Virtulization (SEV) support
405efda core: add new security-policy object
3d2db73 monitor: use debug version of memory access apis
bcb1584 exec: add debug version of physical memory read and write apis
ef720ae exec: add guest RAM read and write ops
bcdc107 memattrs: add debug attrs
=== OUTPUT BEGIN ===
Checking PATCH 1/16: memattrs: add debug attrs...
Checking PATCH 2/16: exec: add guest RAM read and write ops...
Checking PATCH 3/16: exec: add debug version of physical memory read and write apis...
Checking PATCH 4/16: monitor: use debug version of memory access apis...
Checking PATCH 5/16: core: add new security-policy object...
Checking PATCH 6/16: sev: add Secure Encrypted Virtulization (SEV) support...
ERROR: trailing whitespace
#705: FILE: qemu-options.hx:4000:
+SEV-enabled guest. $
ERROR: do not use C99 // comments
#1736: FILE: sev.c:923:
+ // add the command to launch guest in next patches
ERROR: do not use C99 // comments
#1743: FILE: sev.c:930:
+ // add the command to finalize the launch in next patches
ERROR: do not use C99 // comments
#1810: FILE: sev.c:997:
+ // use receive_info commands
ERROR: do not use C99 // comments
#1827: FILE: sev.c:1014:
+ // use launch_finish commands
ERROR: do not use C99 // comments
#1829: FILE: sev.c:1016:
+ // use receive_finish commands
ERROR: do not use C99 // comments
#1844: FILE: sev.c:1031:
+ // fill in the code in next patches
ERROR: do not use C99 // comments
#1855: FILE: sev.c:1042:
+ // fill in the code in next patches
total: 8 errors, 0 warnings, 1775 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.
Checking PATCH 7/16: hmp: display memory encryption support in 'info kvm'...
Checking PATCH 8/16: core: loader: create memory encryption context before copying data...
Checking PATCH 9/16: sev: add LAUNCH_START command...
Checking PATCH 10/16: sev: add LAUNCH_UPDATE command...
Checking PATCH 11/16: sev: add LAUNCH_FINISH command...
Checking PATCH 12/16: sev: add DEBUG_DECRYPT command...
Checking PATCH 13/16: sev: add DEBUG_ENCRYPT command...
Checking PATCH 14/16: i386: set memory encryption ops for PC.BIOS and PC.RAM regions...
Checking PATCH 15/16: target-i386: add cpuid Fn8000_001f...
Checking PATCH 16/16: i386: clear C-bit in SEV guest page table walk...
=== 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
prev parent reply other threads:[~2016-09-22 15:54 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 14:51 [Qemu-devel] [RFC PATCH v2 00/16] x86: Secure Encrypted Virtualization (AMD) Brijesh Singh
2016-09-22 14:52 ` [Qemu-devel] [RFC PATCH v2 01/16] memattrs: add debug attrs Brijesh Singh
2016-09-22 14:52 ` [Qemu-devel] [RFC PATCH v2 02/16] exec: add guest RAM read and write ops Brijesh Singh
2016-09-22 15:22 ` Paolo Bonzini
2016-09-22 14:52 ` [Qemu-devel] [RFC PATCH v2 03/16] exec: add debug version of physical memory read and write apis Brijesh Singh
2016-09-22 15:21 ` Paolo Bonzini
2016-09-22 14:52 ` [Qemu-devel] [RFC PATCH v2 04/16] monitor: use debug version of memory access apis Brijesh Singh
2016-09-22 15:18 ` Paolo Bonzini
2016-09-22 19:24 ` Michael S. Tsirkin
2016-09-22 20:55 ` Brijesh Singh
2016-09-22 14:52 ` [Qemu-devel] [RFC PATCH v2 05/16] core: add new security-policy object Brijesh Singh
2016-09-22 14:52 ` [Qemu-devel] [RFC PATCH v2 06/16] sev: add Secure Encrypted Virtulization (SEV) support Brijesh Singh
2016-09-22 15:12 ` Paolo Bonzini
2016-09-22 21:12 ` Brijesh Singh
2016-09-22 21:57 ` Michael S. Tsirkin
2016-09-22 19:51 ` Michael S. Tsirkin
2016-09-22 14:52 ` [Qemu-devel] [RFC PATCH v2 07/16] hmp: display memory encryption support in 'info kvm' Brijesh Singh
2016-09-22 15:32 ` Eric Blake
2016-09-22 14:53 ` [Qemu-devel] [RFC PATCH v2 08/16] core: loader: create memory encryption context before copying data Brijesh Singh
2016-09-22 14:53 ` [Qemu-devel] [RFC PATCH v2 09/16] sev: add LAUNCH_START command Brijesh Singh
2016-09-22 14:53 ` [Qemu-devel] [RFC PATCH v2 10/16] sev: add LAUNCH_UPDATE command Brijesh Singh
2016-09-22 14:53 ` [Qemu-devel] [RFC PATCH v2 11/16] sev: add LAUNCH_FINISH command Brijesh Singh
2016-09-22 14:53 ` [Qemu-devel] [RFC PATCH v2 12/16] sev: add DEBUG_DECRYPT command Brijesh Singh
2016-09-22 14:54 ` [Qemu-devel] [RFC PATCH v2 13/16] sev: add DEBUG_ENCRYPT command Brijesh Singh
2016-09-22 14:54 ` [Qemu-devel] [RFC PATCH v2 14/16] i386: set memory encryption ops for PC.BIOS and PC.RAM regions Brijesh Singh
2016-09-22 14:54 ` [Qemu-devel] [RFC PATCH v2 15/16] target-i386: add cpuid Fn8000_001f Brijesh Singh
2016-09-22 14:54 ` [Qemu-devel] [RFC PATCH v2 16/16] i386: clear C-bit in SEV guest page table walk Brijesh Singh
2016-09-22 15:53 ` [Qemu-devel] [RFC PATCH v2 00/16] x86: Secure Encrypted Virtualization (AMD) no-reply
2016-09-22 15:54 ` no-reply [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=20160922155409.382041.38351@ex-std-node742.prod.rhcloud.com \
--to=no-reply@patchew.org \
--cc=armbru@redhat.com \
--cc=brijesh.singh@amd.com \
--cc=crosthwaite.peter@gmail.com \
--cc=ehabkost@redhat.com \
--cc=famz@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mst@redhat.com \
--cc=p.fedin@samsung.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).