From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Jake Freeland <jfree@FreeBSD.org>
Subject: |WARNING| pw153331 [PATCH 4/4] bus/pci/bsd: Fix device existence check
Date: Tue, 6 May 2025 19:41:19 +0200 (CEST) [thread overview]
Message-ID: <20250506174119.51C1C123FAA@dpdk.org> (raw)
In-Reply-To: <20250506174046.1136711-5-jfree@FreeBSD.org>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/153331
_coding style issues_
WARNING:REPEATED_WORD: Possible repeated word: 'the'
#103:
device. This avoids a possible race condition where the the device file is
total: 0 errors, 1 warnings, 34 lines checked
next prev parent reply other threads:[~2025-05-06 17:41 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250506174046.1136711-5-jfree@FreeBSD.org>
2025-05-06 17:07 ` |SUCCESS| pw153328-153331 " qemudev
2025-05-06 17:12 ` qemudev
2025-05-06 17:41 ` checkpatch [this message]
2025-05-06 19:04 ` |SUCCESS| pw153331 " 0-day Robot
2025-05-06 21:50 ` |SUCCESS| pw153328-153331 [PATCH] [4/4] bus/pci/bsd: Fix device exis dpdklab
2025-05-06 21:57 ` dpdklab
2025-05-06 22:02 ` dpdklab
2025-05-06 22:07 ` dpdklab
2025-05-06 22:25 ` dpdklab
2025-05-06 22:34 ` dpdklab
2025-05-06 22:38 ` dpdklab
2025-05-06 22:39 ` dpdklab
2025-05-06 22:40 ` |PENDING| " dpdklab
2025-05-06 22:44 ` |SUCCESS| " dpdklab
2025-05-06 22:48 ` dpdklab
2025-05-06 22:48 ` dpdklab
2025-05-06 22:49 ` dpdklab
2025-05-06 22:52 ` dpdklab
2025-05-06 23:01 ` dpdklab
2025-05-06 23:02 ` dpdklab
2025-05-06 23:07 ` dpdklab
2025-05-06 23:08 ` dpdklab
2025-05-06 23:13 ` dpdklab
2025-05-06 23:23 ` |PENDING| " dpdklab
2025-05-06 23:27 ` |SUCCESS| " dpdklab
2025-05-06 23:27 ` |PENDING| " dpdklab
2025-05-06 23:30 ` |SUCCESS| " dpdklab
2025-05-06 23:33 ` |PENDING| " dpdklab
2025-05-07 0:08 ` |SUCCESS| " dpdklab
2025-05-07 0:08 ` dpdklab
2025-05-07 0:13 ` dpdklab
2025-05-07 0:28 ` dpdklab
2025-05-07 0:29 ` dpdklab
2025-05-07 1:01 ` dpdklab
2025-05-07 1:04 ` dpdklab
2025-05-07 1:23 ` dpdklab
2025-05-07 2:05 ` 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=20250506174119.51C1C123FAA@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=jfree@FreeBSD.org \
--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).