From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Erik Carrillo <erik.g.carrillo@intel.com>
Subject: [dpdk-test-report] |WARNING| pw35787 [PATCH v7 1/7] eventtimer: add event timer adapter API
Date: Thu, 8 Mar 2018 22:54:43 +0100 (CET) [thread overview]
Message-ID: <20180308215443.D5DF7AAC4@dpdk.org> (raw)
In-Reply-To: <1520546046-6973-2-git-send-email-erik.g.carrillo@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/35787
_coding style issues_
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#278: FILE: lib/librte_eventdev/rte_event_timer_adapter.h:236:
+struct rte_event_timer_adapter * __rte_experimental
ERROR:POINTER_LOCATION: "foo * bar" should be "foo *bar"
#308: FILE: lib/librte_eventdev/rte_event_timer_adapter.h:266:
+struct rte_event_timer_adapter * __rte_experimental
total: 2 errors, 0 warnings, 702 lines checked
parent reply other threads:[~2018-03-08 21:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1520546046-6973-2-git-send-email-erik.g.carrillo@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=20180308215443.D5DF7AAC4@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=erik.g.carrillo@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).