From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Kevin O'Sullivan <kevin.osullivan@intel.com>
Subject: |WARNING| pw124856 [PATCH 2/2] crypto/qat: added cipher-crc cap check
Date: Wed, 8 Mar 2023 13:14:14 +0100 (CET) [thread overview]
Message-ID: <20230308121414.91C62120D89@dpdk.org> (raw)
In-Reply-To: <20230308121258.88708-3-kevin.osullivan@intel.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/124856
_coding style issues_
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#258: FILE: drivers/common/qat/qat_qp.c:1066:
+ cipher_param = (void *)&cipher_crc_cap_msg.serv_specif_rqpars;
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#272: FILE: drivers/common/qat/qat_qp.c:1080:
+ cipher_crc_cap_msg.comn_hdr.serv_specif_flags,
WARNING:TYPO_SPELLING: 'specif' may be misspelled - perhaps 'specify'?
#629: FILE: drivers/crypto/qat/qat_sym_session.c:2713:
+ ((char *)&req_tmpl->serv_specif_rqpars +
total: 0 errors, 3 warnings, 646 lines checked
next prev parent reply other threads:[~2023-03-08 12:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230308121258.88708-3-kevin.osullivan@intel.com>
2023-03-08 12:02 ` |SUCCESS| pw124855-124856 " qemudev
2023-03-08 12:06 ` qemudev
2023-03-08 12:14 ` checkpatch [this message]
2023-03-08 13:59 ` |SUCCESS| pw124856 " 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=20230308121414.91C62120D89@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=kevin.osullivan@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).