From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-test-report] |WARNING| pw92008 [RFC PATCH] devtools: script to check meson indentation of lists
Date: Thu, 22 Apr 2021 11:03:48 +0200 (CEST) [thread overview]
Message-ID: <20210422090348.3B975121158@dpdk.org> (raw)
In-Reply-To: <20210422090211.320855-1-bruce.richardson@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/92008
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#60:
This is a draft script developed when I was working on the whitespace rework
WARNING:TYPO_SPELLING: 'files'' may be misspelled - perhaps 'file's'?
#171: FILE: devtools/dpdk_meson_check.py:94:
+ parser = ArgumentParser(description='Run syntax checks on DPDK meson.build files')
WARNING:TYPO_SPELLING: 'process'' may be misspelled - perhaps 'process's'?
#172: FILE: devtools/dpdk_meson_check.py:95:
+ parser.add_argument('-d', metavar='directory', default='.', help='Directory to process')
total: 0 errors, 3 warnings, 106 lines checked
parent reply other threads:[~2021-04-22 9:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20210422090211.320855-1-bruce.richardson@intel.com>]
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=20210422090348.3B975121158@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=bruce.richardson@intel.com \
--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).