From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Shani Peretz <shperetz@nvidia.com>
Subject: |WARNING| pw150593 [PATCH v4] bus: fix inconsistent representation of PCI numbers
Date: Wed, 29 Jan 2025 09:55:23 +0100 (CET) [thread overview]
Message-ID: <20250129085523.BDE3E126FF4@dpdk.org> (raw)
In-Reply-To: <20250129085416.226718-1-shperetz@nvidia.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/150593
_coding style issues_
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#247: FILE: app/test/test_devargs.c:311:
+ uint8_t slave_mac1[] = {0x00, 0xFF, 0x00, 0xFF, 0x00, 0x00 };
WARNING:TYPO_SPELLING: 'slave' may be misspelled - perhaps 'secondary'?
#248: FILE: app/test/test_devargs.c:312:
+ struct rte_ether_addr *mac_addr = (struct rte_ether_addr *)slave_mac1;
total: 0 errors, 2 warnings, 739 lines checked
Warning in app/test/test_devargs.c:
Using driver specific headers in applications
next prev parent reply other threads:[~2025-01-29 8:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250129085416.226718-1-shperetz@nvidia.com>
2025-01-29 8:21 ` |SUCCESS| " qemudev
2025-01-29 8:25 ` |FAILURE| " qemudev
2025-01-29 8:55 ` checkpatch [this message]
2025-01-29 10:01 ` |SUCCESS| pw150593 [PATCH] [v4] bus: fix inconsistent representation dpdklab
2025-01-29 10:05 ` |FAILURE| pw150593 [PATCH v4] bus: fix inconsistent representation of PCI numbers 0-day Robot
2025-01-29 10:06 ` |SUCCESS| pw150593 [PATCH] [v4] bus: fix inconsistent representation dpdklab
2025-01-29 10:11 ` |FAILURE| " dpdklab
2025-01-29 10:13 ` dpdklab
2025-01-29 10:15 ` |SUCCESS| " dpdklab
2025-01-29 10:19 ` |WARNING| " dpdklab
2025-01-29 10:24 ` |FAILURE| " dpdklab
2025-01-29 10:29 ` |PENDING| " dpdklab
2025-01-29 10:38 ` |WARNING| " dpdklab
2025-01-29 10:47 ` |PENDING| " dpdklab
2025-01-29 10:50 ` |WARNING| " dpdklab
2025-01-29 10:57 ` |PENDING| " dpdklab
2025-01-29 11:14 ` |FAILURE| " dpdklab
2025-01-29 11:46 ` |SUCCESS| " dpdklab
2025-01-29 12:58 ` |WARNING| " dpdklab
2025-01-29 13:28 ` dpdklab
2025-01-29 15:22 ` |FAILURE| " dpdklab
2025-01-29 17:43 ` |SUCCESS| " dpdklab
2025-01-30 2:26 ` |FAILURE| " dpdklab
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=20250129085523.BDE3E126FF4@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=shperetz@nvidia.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).