From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Shreyansh Jain <shreyansh.jain@nxp.com>
Subject: [dpdk-test-report] |WARNING| pw24760 [PATCH RFC 08/39] bus/dpaa: add FMan hardware operations
Date: Sat, 27 May 2017 12:19:20 +0200 (CEST) [thread overview]
Message-ID: <20170527101920.E0FD17D04@dpdk.org> (raw)
In-Reply-To: <1495880735-1651-9-git-send-email-shreyansh.jain@nxp.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/24760
_coding style issues_
WARNING:FUNCTION_ARGUMENTS: function definition argument 'struct fman_if *' should also have an identifier name
#778: FILE: drivers/bus/dpaa/include/fsl_fman.h:108:
+void fman_if_promiscuous_enable(struct fman_if *);
WARNING:FUNCTION_ARGUMENTS: function definition argument 'struct fman_if *' should also have an identifier name
#779: FILE: drivers/bus/dpaa/include/fsl_fman.h:109:
+void fman_if_promiscuous_disable(struct fman_if *);
WARNING:FUNCTION_ARGUMENTS: function definition argument 'struct fman_if *' should also have an identifier name
#782: FILE: drivers/bus/dpaa/include/fsl_fman.h:112:
+void fman_if_enable_rx(struct fman_if *);
WARNING:FUNCTION_ARGUMENTS: function definition argument 'struct fman_if *' should also have an identifier name
#783: FILE: drivers/bus/dpaa/include/fsl_fman.h:113:
+void fman_if_disable_rx(struct fman_if *);
WARNING:FUNCTION_ARGUMENTS: function definition argument 'struct fman_if *' should also have an identifier name
#786: FILE: drivers/bus/dpaa/include/fsl_fman.h:116:
+void fman_if_loopback_enable(struct fman_if *);
WARNING:FUNCTION_ARGUMENTS: function definition argument 'struct fman_if *' should also have an identifier name
#787: FILE: drivers/bus/dpaa/include/fsl_fman.h:117:
+void fman_if_loopback_disable(struct fman_if *);
total: 0 errors, 6 warnings, 1066 lines checked
parent reply other threads:[~2017-05-27 10:19 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1495880735-1651-9-git-send-email-shreyansh.jain@nxp.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=20170527101920.E0FD17D04@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=shreyansh.jain@nxp.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).