From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Baruch Siach <baruch@tkos.co.il>
Subject: [dpdk-test-report] |WARNING| [PATCH] doc: correct description of attach to indirect mbuf
Date: Tue, 6 Dec 2016 09:16:18 +0100 (CET) [thread overview]
Message-ID: <20161206081618.1E9FD2BDD@dpdk.org> (raw)
In-Reply-To: <f4057510c794c0e18d1677eda7e3cbf18e3de530.1481012155.git.baruch@tkos.co.il>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/17699
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#39:
Since commit 4a96e8b652 ("mbuf: allow to clone an indirect mbuf") attaching to
ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit 0123456789ab ("mbuf: allow to clone an indirect mbuf")'
#39:
Since commit 4a96e8b652 ("mbuf: allow to clone an indirect mbuf") attaching to
total: 1 errors, 1 warnings, 9 lines checked
parent reply other threads:[~2016-12-06 8:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <f4057510c794c0e18d1677eda7e3cbf18e3de530.1481012155.git.baruch@tkos.co.il>]
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=20161206081618.1E9FD2BDD@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=baruch@tkos.co.il \
--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).