automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Radu Nicolau <radu.nicolau@intel.com>
Subject: [dpdk-test-report] |WARNING| pw95800 [RFC 06/10] ipsec: add transmit segmentation offload support
Date: Tue, 13 Jul 2021 15:45:54 +0200 (CEST)	[thread overview]
Message-ID: <20210713134554.A5104120F1F@dpdk.org> (raw)
In-Reply-To: <20210713133241.3550051-7-radu.nicolau@intel.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/95800

_coding style issues_


WARNING:TYPO_SPELLING: 'segements' may be misspelled - perhaps 'segments'?
#174: FILE: lib/ipsec/esp_outb.c:677:
+	uint16_t segements = 1;

WARNING:TYPO_SPELLING: 'segements' may be misspelled - perhaps 'segments'?
#179: FILE: lib/ipsec/esp_outb.c:682:
+		return segements;

WARNING:TYPO_SPELLING: 'segements' may be misspelled - perhaps 'segments'?
#182: FILE: lib/ipsec/esp_outb.c:685:
+		segements = ceil((float)pkt_l3len / sa->tso.mss);

WARNING:TYPO_SPELLING: 'segements' may be misspelled - perhaps 'segments'?
#195: FILE: lib/ipsec/esp_outb.c:698:
+	return segements;

total: 0 errors, 4 warnings, 271 lines checked

           reply	other threads:[~2021-07-13 13:45 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20210713133241.3550051-7-radu.nicolau@intel.com>]

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=20210713134554.A5104120F1F@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=radu.nicolau@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).