From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
Subject: |WARNING| pw109331 [RFC PATCH v1 5/8] dts: merge DTS vm_images/README.md to DPDK
Date: Wed, 6 Apr 2022 17:33:41 +0200 (CEST) [thread overview]
Message-ID: <20220406153341.614D3122BA2@dpdk.org> (raw)
In-Reply-To: <20220406153151.2917346-6-juraj.linkes@pantheon.tech>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/109331
_coding style issues_
WARNING:COMMIT_MESSAGE: Missing commit description - Add an appropriate one
ERROR:TRAILING_WHITESPACE: trailing whitespace
#68: FILE: dts/vm_images/README.md:3:
+This folder contains utilities to create VM $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#74: FILE: dts/vm_images/README.md:9:
+and set up. $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#86: FILE: dts/vm_images/README.md:21:
+it will build them. $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#88: FILE: dts/vm_images/README.md:23:
+The root password it asks for is what to set the VM's $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#90: FILE: dts/vm_images/README.md:25:
+you run the script on. $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#92: FILE: dts/vm_images/README.md:27:
+``` --debug ``` will enable debug output from guestfs $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#99: FILE: dts/vm_images/README.md:34:
+Most distros will have a "cloud image" which is in the $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#108: FILE: dts/vm_images/README.md:43:
+Currently, only RHEL 8 family distros and Ubuntu 20.04 are $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#110: FILE: dts/vm_images/README.md:45:
+testing has gone to Ubuntu 20.04. $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#114: FILE: dts/vm_images/README.md:49:
+Due to the way that guestfs tools work, they must run $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#115: FILE: dts/vm_images/README.md:50:
+under kvm, but the host needs to have a kernel image $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#117: FILE: dts/vm_images/README.md:52:
+to work around this issue using containers, but $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#118: FILE: dts/vm_images/README.md:53:
+several days of experimentation kept running into $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#121: FILE: dts/vm_images/README.md:56:
+your best bet is to build your VMs on either a $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#123: FILE: dts/vm_images/README.md:58:
+or inside a VM already being emulated as your desired $
ERROR:TRAILING_WHITESPACE: trailing whitespace
#125: FILE: dts/vm_images/README.md:60:
+issues with the hypervisor, since not all hypervisors $
ERROR:MISSING_SIGN_OFF: Missing Signed-off-by: line(s)
total: 17 errors, 1 warnings, 64 lines checked
parent reply other threads:[~2022-04-06 15:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220406153151.2917346-6-juraj.linkes@pantheon.tech>]
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=20220406153341.614D3122BA2@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=juraj.linkes@pantheon.tech \
--cc=test-report@dpdk.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).