From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: |WARNING| pw152303 [PATCH 2/2] net/bnxt: fix epoch bit calculation
Date: Mon, 10 Mar 2025 22:02:35 +0100 (CET) [thread overview]
Message-ID: <20250310210235.2A6AA127D1C@dpdk.org> (raw)
In-Reply-To: <20250310210132.48829-3-ajit.khaparde@broadcom.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/152303
_coding style issues_
WARNING:TYPO_SPELLING: 'cace' may be misspelled - perhaps 'cache'?
#95:
Fixes: 30656a1cace8 ("net/bnxt: refactor epoch setting")
total: 0 errors, 1 warnings, 0 checks, 73 lines checked
next prev parent reply other threads:[~2025-03-10 21:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250310210132.48829-3-ajit.khaparde@broadcom.com>
2025-03-10 20:27 ` |SUCCESS| pw152302-152303 " qemudev
2025-03-10 20:31 ` qemudev
2025-03-10 21:02 ` checkpatch [this message]
2025-03-10 21:36 ` |SUCCESS| pw152302-152303 [PATCH] [2/2] net/bnxt: fix epoch bit calc dpdklab
2025-03-10 21:42 ` dpdklab
2025-03-10 21:44 ` dpdklab
2025-03-10 21:44 ` |PENDING| " dpdklab
2025-03-10 21:45 ` |SUCCESS| " dpdklab
2025-03-10 21:53 ` |PENDING| " dpdklab
2025-03-10 21:54 ` dpdklab
2025-03-10 21:57 ` |SUCCESS| " dpdklab
2025-03-10 22:03 ` |SUCCESS| pw152303 [PATCH 2/2] net/bnxt: fix epoch bit calculation 0-day Robot
2025-03-10 22:07 ` |FAILURE| pw152302-152303 [PATCH] [2/2] net/bnxt: fix epoch bit calc dpdklab
2025-03-10 22:12 ` |SUCCESS| " dpdklab
2025-03-10 22:13 ` |FAILURE| " dpdklab
2025-03-10 22:16 ` dpdklab
2025-03-10 22:19 ` |SUCCESS| " dpdklab
2025-03-10 22:19 ` dpdklab
2025-03-10 22:22 ` |FAILURE| " dpdklab
2025-03-10 22:22 ` dpdklab
2025-03-10 22:27 ` dpdklab
2025-03-10 22:31 ` dpdklab
2025-03-10 22:34 ` dpdklab
2025-03-10 22:47 ` dpdklab
2025-03-10 22:52 ` |SUCCESS| " dpdklab
2025-03-10 22:52 ` |FAILURE| " dpdklab
2025-03-10 23:11 ` |SUCCESS| " dpdklab
2025-03-10 23:46 ` dpdklab
2025-03-11 0:35 ` 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=20250310210235.2A6AA127D1C@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=ajit.khaparde@broadcom.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).