From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: |WARNING| pw150647 [PATCH] dma/idxd: add device ids for new HW versions
Date: Thu, 30 Jan 2025 18:26:54 +0100 (CET) [thread overview]
Message-ID: <20250130172654.4BA89124126@dpdk.org> (raw)
In-Reply-To: <20250130172624.1450975-2-bruce.richardson@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/150647
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#72:
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/dma/idxd/registers.h#n9
total: 0 errors, 1 warnings, 35 lines checked
next prev parent reply other threads:[~2025-01-30 17:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250130172624.1450975-2-bruce.richardson@intel.com>
2025-01-30 16:53 ` |SUCCESS| " qemudev
2025-01-30 16:57 ` qemudev
2025-01-30 17:26 ` checkpatch [this message]
2025-01-30 18:23 ` 0-day Robot
2025-01-30 18:27 ` |FAILURE| pw150647 [PATCH] dma/idxd: add device ids for new HW versi dpdklab
2025-01-30 18:46 ` |PENDING| " dpdklab
2025-01-30 18:46 ` dpdklab
2025-01-30 18:47 ` |SUCCESS| " dpdklab
2025-01-30 18:48 ` dpdklab
2025-01-30 18:51 ` dpdklab
2025-01-30 18:51 ` dpdklab
2025-01-30 20:14 ` dpdklab
2025-01-30 20:26 ` |PENDING| " dpdklab
2025-01-30 21:29 ` |SUCCESS| " dpdklab
2025-01-30 21:36 ` dpdklab
2025-01-30 23:16 ` |WARNING| " dpdklab
2025-01-30 23:19 ` dpdklab
2025-01-30 23:19 ` dpdklab
2025-01-30 23:24 ` dpdklab
2025-01-30 23:45 ` dpdklab
2025-01-31 0:23 ` |PENDING| " dpdklab
2025-01-31 1:09 ` |SUCCESS| " 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=20250130172654.4BA89124126@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=bruce.richardson@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).