From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: gnandiba@amd.com
Subject: [dpdk-test-report] |WARNING| pw84651 [PATCH v1] net/axgbe: enabling VLAN support in axgbe
Date: Tue, 1 Dec 2020 09:08:13 +0100 (CET) [thread overview]
Message-ID: <20201201080813.519A3C9A0@dpdk.org> (raw)
In-Reply-To: <20201201080652.9990-1-gnandiba@amd.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/84651
_coding style issues_
WARNING:FUNCTION_ARGUMENTS: function definition argument 'struct axgbe_port *' should also have an identifier name
#661: FILE: drivers/net/axgbe/axgbe_ethdev.h:303:
+ int (*enable_rx_vlan_stripping)(struct axgbe_port *);
WARNING:FUNCTION_ARGUMENTS: function definition argument 'struct axgbe_port *' should also have an identifier name
#662: FILE: drivers/net/axgbe/axgbe_ethdev.h:304:
+ int (*disable_rx_vlan_stripping)(struct axgbe_port *);
WARNING:FUNCTION_ARGUMENTS: function definition argument 'struct axgbe_port *' should also have an identifier name
#663: FILE: drivers/net/axgbe/axgbe_ethdev.h:305:
+ int (*enable_rx_vlan_filtering)(struct axgbe_port *);
WARNING:FUNCTION_ARGUMENTS: function definition argument 'struct axgbe_port *' should also have an identifier name
#664: FILE: drivers/net/axgbe/axgbe_ethdev.h:306:
+ int (*disable_rx_vlan_filtering)(struct axgbe_port *);
WARNING:FUNCTION_ARGUMENTS: function definition argument 'struct axgbe_port *' should also have an identifier name
#665: FILE: drivers/net/axgbe/axgbe_ethdev.h:307:
+ int (*update_vlan_hash_table)(struct axgbe_port *);
total: 0 errors, 5 warnings, 0 checks, 645 lines checked
next parent reply other threads:[~2020-12-01 8:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201201080652.9990-1-gnandiba@amd.com>
2020-12-01 8:08 ` checkpatch [this message]
2020-12-01 10:36 ` [dpdk-test-report] |WARNING| pw84651 " 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=20201201080813.519A3C9A0@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=gnandiba@amd.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).