From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Nicolas Chautru <nicolas.chautru@intel.com>
Subject: |WARNING| pw135834 [PATCH v1 1/1] baseband/acc: refactor of DMA response
Date: Wed, 10 Jan 2024 23:37:26 +0100 (CET) [thread overview]
Message-ID: <20240110223726.2D98E12485B@dpdk.org> (raw)
In-Reply-To: <20240110222822.832395-2-nicolas.chautru@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/135834
_coding style issues_
WARNING:TYPO_SPELLING: 'explictly' may be misspelled - perhaps 'explicitly'?
#106: FILE: drivers/baseband/acc/rte_vrb_pmd.c:3100:
+ /* Clear response explictly. */
total: 0 errors, 1 warnings, 237 lines checked
next prev parent reply other threads:[~2024-01-10 22:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240110222822.832395-2-nicolas.chautru@intel.com>
2024-01-10 22:17 ` |SUCCESS| " qemudev
2024-01-10 22:21 ` qemudev
2024-01-10 22:37 ` checkpatch [this message]
2024-01-10 23:24 ` 0-day Robot
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=20240110223726.2D98E12485B@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=nicolas.chautru@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).