From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Harman Kalra <hkalra@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw96547 [PATCH] doc: announce: make rte intr handle internal
Date: Mon, 2 Aug 2021 18:05:43 +0200 (CEST) [thread overview]
Message-ID: <20210802160543.925B8123658@dpdk.org> (raw)
In-Reply-To: <20210802160352.135754-1-hkalra@marvell.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/96547
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#88:
https://docs.google.com/spreadsheets/d/1betlC000ua5SsSiJIcC54mCCCJnW6voH5Dqv9UxeyfE/edit#gid=0
total: 0 errors, 1 warnings, 9 lines checked
next parent reply other threads:[~2021-08-02 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210802160352.135754-1-hkalra@marvell.com>
2021-08-02 16:05 ` checkpatch [this message]
2021-08-02 16:38 ` [dpdk-test-report] |SUCCESS| pw96547 [dpdk-dev] " 0-day Robot
2021-08-02 18:30 [dpdk-test-report] |WARNING| pw96547 " dpdklab
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=20210802160543.925B8123658@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=hkalra@marvell.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).