From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Anatoly Burakov <anatoly.burakov@intel.com>
Subject: |WARNING| pw143545 [PATCH v1 10/30] net/i40e/base: add definitions for rx_err1
Date: Mon, 2 Sep 2024 11:58:09 +0200 (CEST) [thread overview]
Message-ID: <20240902095809.1126D122DDC@dpdk.org> (raw)
In-Reply-To: <46a3504047a45912739bf6ea58f94fd48d463e5a.1725270827.git.anatoly.burakov@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/143545
_coding style issues_
WARNING:LONG_LINE_COMMENT: line length of 101 exceeds 100 columns
#111: FILE: drivers/net/i40e/base/i40e_register.h:2394:
+#define I40E_GL_RXERR1H(_i) (0x00318004 + ((_i) * 8)) /* _i=0...143 */ /* Reset: CORER */
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#113: FILE: drivers/net/i40e/base/i40e_register.h:2396:
+#define I40E_GL_RXERR1H_RXERR1H_SHIFT ^I0$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#114: FILE: drivers/net/i40e/base/i40e_register.h:2397:
+#define I40E_GL_RXERR1H_RXERR1H_MASK ^II40E_MASK(0xFFFFFFFF, I40E_GL_RXERR1H_RXERR1H_SHIFT)$
WARNING:LONG_LINE_COMMENT: line length of 101 exceeds 100 columns
#115: FILE: drivers/net/i40e/base/i40e_register.h:2398:
+#define I40E_GL_RXERR1L(_i) (0x00318000 + ((_i) * 8)) /* _i=0...143 */ /* Reset: CORER */
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#117: FILE: drivers/net/i40e/base/i40e_register.h:2400:
+#define I40E_GL_RXERR1L_RXERR1L_SHIFT ^I0$
WARNING:SPACE_BEFORE_TAB: please, no space before tabs
#118: FILE: drivers/net/i40e/base/i40e_register.h:2401:
+#define I40E_GL_RXERR1L_RXERR1L_MASK ^II40E_MASK(0xFFFFFFFF, I40E_GL_RXERR1L_RXERR1L_SHIFT)$
total: 0 errors, 6 warnings, 0 checks, 106 lines checked
parent reply other threads:[~2024-09-02 9:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <46a3504047a45912739bf6ea58f94fd48d463e5a.1725270827.git.anatoly.burakov@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=20240902095809.1126D122DDC@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=anatoly.burakov@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).