From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Andre Muezerie <andremue@linux.microsoft.com>
Subject: |WARNING| pw152273 [PATCH v3 2/2] devtools/dump-cpu-flags: add tool to update CPU flags table
Date: Thu, 6 Mar 2025 20:10:20 +0100 (CET) [thread overview]
Message-ID: <20250306191020.3C826127D12@dpdk.org> (raw)
In-Reply-To: <1741288114-15179-3-git-send-email-andremue@linux.microsoft.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/152273
_coding style issues_
WARNING:TYPO_SPELLING: 'SSEE' may be misspelled - perhaps 'SEE'?
#272: FILE: devtools/dump-cpu-flags/dump-cpu-flags.cpp:29:
+ cpu_flags.push_back("SSEE3");
total: 0 errors, 1 warnings, 305 lines checked
next prev parent reply other threads:[~2025-03-06 19:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1741288114-15179-3-git-send-email-andremue@linux.microsoft.com>
2025-03-06 19:03 ` |SUCCESS| pw152272-152273 " qemudev
2025-03-06 19:07 ` qemudev
2025-03-06 19:10 ` checkpatch [this message]
2025-03-06 19:40 ` |SUCCESS| pw152272-152273 [PATCH] [v3,2/2] devtools/dump-cpu-flags: dpdklab
2025-03-06 19:42 ` |PENDING| " dpdklab
2025-03-06 19:43 ` |SUCCESS| " dpdklab
2025-03-06 19:45 ` |PENDING| " dpdklab
2025-03-06 19:46 ` |SUCCESS| " dpdklab
2025-03-06 19:50 ` dpdklab
2025-03-06 19:59 ` dpdklab
2025-03-06 20:04 ` |PENDING| " dpdklab
2025-03-06 20:06 ` dpdklab
2025-03-06 20:09 ` |SUCCESS| " dpdklab
2025-03-06 20:16 ` dpdklab
2025-03-06 20:19 ` dpdklab
2025-03-06 20:24 ` |SUCCESS| pw152273 [PATCH v3 2/2] devtools/dump-cpu-flags: add tool to update CPU flags table 0-day Robot
2025-03-06 20:26 ` |SUCCESS| pw152272-152273 [PATCH] [v3,2/2] devtools/dump-cpu-flags: dpdklab
2025-03-06 20:48 ` dpdklab
2025-03-06 20:59 ` dpdklab
2025-03-06 21:39 ` dpdklab
2025-03-06 22:44 ` 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=20250306191020.3C826127D12@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=andremue@linux.microsoft.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).