From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Chengwen Feng <fengchengwen@huawei.com>
Subject: |WARNING| pw138444 [PATCH v3 6/6] argparse: fix doc don't display two hyphens
Date: Mon, 18 Mar 2024 10:22:22 +0100 (CET) [thread overview]
Message-ID: <20240318092222.95B321223F7@dpdk.org> (raw)
In-Reply-To: <20240318091848.14360-7-fengchengwen@huawei.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/138444
_coding style issues_
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#67:
[1] https://stackoverflow.com/questions/51075907/display-two-dashes-in-rst-file
total: 0 errors, 1 warnings, 110 lines checked
next prev parent reply other threads:[~2024-03-18 9:22 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240318091848.14360-7-fengchengwen@huawei.com>
2024-03-18 8:59 ` |SUCCESS| pw138446-138444 " qemudev
2024-03-18 9:03 ` qemudev
2024-03-18 9:22 ` checkpatch [this message]
2024-03-18 10:24 ` |SUCCESS| pw138444 " 0-day Robot
2024-03-18 10:27 ` |SUCCESS| pw138446-138444 [PATCH] [v3,6/6] argparse: fix doc don't d dpdklab
2024-03-18 10:28 ` dpdklab
2024-03-18 10:29 ` dpdklab
2024-03-18 10:29 ` dpdklab
2024-03-18 10:29 ` dpdklab
2024-03-18 10:30 ` dpdklab
2024-03-18 10:30 ` dpdklab
2024-03-18 10:31 ` dpdklab
2024-03-18 10:31 ` dpdklab
2024-03-18 10:31 ` dpdklab
2024-03-18 10:31 ` dpdklab
2024-03-18 10:31 ` dpdklab
2024-03-18 10:46 ` dpdklab
2024-03-18 10:47 ` dpdklab
2024-03-18 10:47 ` dpdklab
2024-03-18 10:48 ` dpdklab
2024-03-18 10:49 ` dpdklab
2024-03-18 10:49 ` dpdklab
2024-03-18 10:50 ` dpdklab
2024-03-18 10:50 ` dpdklab
2024-03-18 10:50 ` dpdklab
2024-03-18 10:50 ` dpdklab
2024-03-18 10:50 ` dpdklab
2024-03-18 10:51 ` dpdklab
2024-03-18 10:51 ` dpdklab
2024-03-18 10:52 ` dpdklab
2024-03-18 10:52 ` dpdklab
2024-03-18 10:52 ` dpdklab
2024-03-18 10:53 ` dpdklab
2024-03-18 10:53 ` dpdklab
2024-03-18 10:53 ` dpdklab
2024-03-18 10:53 ` dpdklab
2024-03-18 10:54 ` dpdklab
2024-03-18 10:54 ` dpdklab
2024-03-18 10:54 ` dpdklab
2024-03-18 10:54 ` dpdklab
2024-03-18 10:55 ` dpdklab
2024-03-18 10:55 ` dpdklab
2024-03-18 10:55 ` dpdklab
2024-03-18 10:55 ` dpdklab
2024-03-18 10:56 ` dpdklab
2024-03-18 10:57 ` dpdklab
2024-03-18 10:58 ` dpdklab
2024-03-18 10:59 ` dpdklab
2024-03-18 10:59 ` dpdklab
2024-03-18 11:00 ` dpdklab
2024-03-18 11:01 ` dpdklab
2024-03-18 11:03 ` dpdklab
2024-03-18 11:08 ` dpdklab
2024-03-18 11:09 ` dpdklab
2024-03-18 11:09 ` dpdklab
2024-03-18 11:11 ` dpdklab
2024-03-18 11:15 ` dpdklab
2024-03-18 11:16 ` dpdklab
2024-03-18 11:16 ` dpdklab
2024-03-18 11:17 ` dpdklab
2024-03-18 11:18 ` dpdklab
2024-03-18 11:19 ` dpdklab
2024-03-18 11:19 ` dpdklab
2024-03-18 11:20 ` dpdklab
2024-03-18 11:20 ` dpdklab
2024-03-18 11:39 ` dpdklab
2024-03-18 11:40 ` dpdklab
2024-03-18 11:40 ` dpdklab
2024-03-18 12:21 ` dpdklab
2024-03-18 12:31 ` dpdklab
2024-03-20 11:57 ` dpdklab
2024-03-20 12:33 ` 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=20240318092222.95B321223F7@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=fengchengwen@huawei.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).