automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Vamsi Krishna <vattunuru@marvell.com>
Subject: |WARNING| pw144051 [RFC v0 1/1] dmadev: provide priority configuration support
Date: Fri, 13 Sep 2024 14:12:27 +0200 (CEST)	[thread overview]
Message-ID: <20240913121227.19EFF121D10@dpdk.org> (raw)
In-Reply-To: <20240913121038.315714-1-vattunuru@marvell.com>

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

_coding style issues_


WARNING:TYPO_SPELLING: 'prioirty' may be misspelled - perhaps 'priority'?
#170: FILE: lib/dmadev/rte_dmadev.h:339:
+	/* The prioirty of the DMA HW channel.

total: 0 errors, 1 warnings, 60 lines checked

  parent reply	other threads:[~2024-09-13 12:12 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240913121038.315714-1-vattunuru@marvell.com>
2024-09-13 11:44 ` |SUCCESS| " qemudev
2024-09-13 11:49 ` qemudev
2024-09-13 12:12 ` checkpatch [this message]
2024-09-13 13:04 ` 0-day Robot
2024-09-13 13:08 ` |PENDING| pw144051 [PATCH] [RFC,v0,1/1] dmadev: provide priority con dpdklab
2024-09-13 13:08 ` |SUCCESS| " dpdklab
2024-09-13 13:10 ` dpdklab
2024-09-13 13:13 ` |PENDING| " dpdklab
2024-09-13 13:15 ` |SUCCESS| " dpdklab
2024-09-13 13:16 ` dpdklab
2024-09-13 13:20 ` |PENDING| " dpdklab
2024-09-13 13:27 ` dpdklab
2024-09-13 13:30 ` |SUCCESS| " dpdklab
2024-09-13 13:37 ` dpdklab
2024-09-13 13:38 ` dpdklab
2024-09-13 13:39 ` |PENDING| " dpdklab
2024-09-13 13:44 ` |SUCCESS| " dpdklab
2024-09-13 14:11 ` dpdklab
2024-09-13 14:17 ` dpdklab
2024-09-13 14:28 ` dpdklab
2024-09-13 14:35 ` dpdklab
2024-09-13 14:35 ` dpdklab
2024-09-13 14:36 ` dpdklab
2024-09-13 14:37 ` dpdklab
2024-09-13 14:38 ` dpdklab
2024-09-13 17:39 ` dpdklab
2024-09-15  1:21 ` dpdklab
2024-09-15  4:49 ` dpdklab
2024-09-18  4:57 ` 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=20240913121227.19EFF121D10@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=test-report@dpdk.org \
    --cc=vattunuru@marvell.com \
    /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).