From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-test-report] |WARNING| pw64835 [PATCH 2/2] doc/api: track header files to rebuild docs on change
Date: Fri, 17 Jan 2020 12:26:35 +0100 (CET) [thread overview]
Message-ID: <20200117112635.3039DFFA@dpdk.org> (raw)
In-Reply-To: <20200117112236.5225-3-bruce.richardson@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/64835
_coding style issues_
WARNING:LONG_LINE: line over 90 characters
#73: FILE: doc/api/generate_doxygen.sh:11:
+echo "$OUTDIR: $(awk '/Preprocessing/ {printf("%s ", substr($2, 1, length($2) - 3))}' doxygen.out)" > $OUTDIR.d
total: 0 errors, 1 warnings, 24 lines checked
next parent reply other threads:[~2020-01-17 11:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200117112236.5225-3-bruce.richardson@intel.com>
2020-01-17 11:26 ` checkpatch [this message]
2020-01-17 16:01 ` [dpdk-test-report] |WARNING| pw64835 " 0-day Robot
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=20200117112635.3039DFFA@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).