From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Nandini Persad <nandinipersad361@gmail.com>
Subject: |WARNING| pw148387 [PATCH] doc/guides: add security document
Date: Wed, 13 Nov 2024 05:39:37 +0100 (CET) [thread overview]
Message-ID: <20241113043937.0BC861234FA@dpdk.org> (raw)
In-Reply-To: <20241113043813.67751-1-nandinipersad361@gmail.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/148387
_coding style issues_
WARNING:REPEATED_WORD: Possible repeated word: 'and'
#139: FILE: doc/guides/security/index.rst:28:
+ This library is the glue between ethdev and and crypto dev. It includes low-level supported protocols such as MACsec, TLS, IPSec, and PDCP.
total: 0 errors, 1 warnings, 340 lines checked
Warning in doc/guides/security/index.rst:
Using explicit URL to doc.dpdk.org, prefer :ref: or :doc:
next prev parent reply other threads:[~2024-11-13 4:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241113043813.67751-1-nandinipersad361@gmail.com>
2024-11-13 4:07 ` |SUCCESS| " qemudev
2024-11-13 4:11 ` qemudev
2024-11-13 4:39 ` checkpatch [this message]
2024-11-13 5:25 ` 0-day Robot
2024-11-13 6:58 ` dpdklab
2024-11-13 7:56 ` dpdklab
2024-11-13 8:29 ` dpdklab
2024-11-13 8:34 ` dpdklab
2024-11-13 8:57 ` dpdklab
2024-11-13 9:00 ` dpdklab
2024-11-13 9:00 ` dpdklab
2024-11-13 9:19 ` dpdklab
2024-11-13 9:45 ` dpdklab
2024-11-13 10:05 ` dpdklab
2024-11-13 10:52 ` dpdklab
2024-11-13 11:41 ` dpdklab
2024-11-13 12:36 ` |WARNING| " dpdklab
2024-11-13 12:40 ` dpdklab
2024-11-13 12:49 ` |SUCCESS| " dpdklab
2024-11-13 13:50 ` dpdklab
2024-11-13 14:11 ` dpdklab
2024-11-13 14:45 ` |WARNING| " dpdklab
2024-11-13 14:49 ` dpdklab
2024-11-13 14:50 ` |SUCCESS| " dpdklab
2024-11-13 16:18 ` dpdklab
2024-11-13 17:45 ` |WARNING| " dpdklab
2024-11-14 0:47 ` dpdklab
2024-11-14 3:00 ` 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=20241113043937.0BC861234FA@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=nandinipersad361@gmail.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).