automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Bruce Richardson <bruce.richards@intel.com>
Subject: |WARNING| pw143148 [RFC PATCH v2 26/26] config: add computed max queues define for compatibility
Date: Wed, 14 Aug 2024 09:52:14 +0200 (CEST)	[thread overview]
Message-ID: <20240814075214.ACC22123EFA@dpdk.org> (raw)
In-Reply-To: <20240813160003.423935-27-bruce.richards@intel.com>

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

_coding style issues_


WARNING:FROM_SIGN_OFF_MISMATCH: From:/Signed-off-by: email address mismatch: 'From: Bruce Richardson <bruce.richards@intel.com>' != 'Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>'

total: 0 errors, 1 warnings, 47 lines checked

  parent reply	other threads:[~2024-08-14  7:52 UTC|newest]

Thread overview: 94+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240813160003.423935-27-bruce.richards@intel.com>
2024-08-14  7:27 ` |SUCCESS| pw143123-143148 " qemudev
2024-08-14  7:32 ` qemudev
2024-08-14  7:52 ` checkpatch [this message]
2024-08-14  9:33 ` |SUCCESS| pw143123-143148 [PATCH] [RFC,v2,26/26] config: add compute dpdklab
2024-08-14  9:35 ` |PENDING| " dpdklab
2024-08-14  9:38 ` |SUCCESS| " dpdklab
2024-08-14  9:39 ` dpdklab
2024-08-14  9:42 ` dpdklab
2024-08-14  9:42 ` dpdklab
2024-08-14  9:43 ` dpdklab
2024-08-14  9:48 ` dpdklab
2024-08-14  9:48 ` dpdklab
2024-08-14  9:49 ` dpdklab
2024-08-14  9:50 ` dpdklab
2024-08-14  9:55 ` dpdklab
2024-08-14 10:02 ` dpdklab
2024-08-14 10:03 ` dpdklab
2024-08-14 10:08 ` dpdklab
2024-08-14 10:23 ` dpdklab
2024-08-14 10:25 ` dpdklab
2024-08-14 10:25 ` |PENDING| " dpdklab
2024-08-14 10:29 ` dpdklab
2024-08-14 10:30 ` dpdklab
2024-08-14 10:34 ` dpdklab
2024-08-14 10:35 ` dpdklab
2024-08-14 10:37 ` dpdklab
2024-08-14 10:39 ` |SUCCESS| " dpdklab
2024-08-14 10:39 ` |PENDING| " dpdklab
2024-08-14 10:44 ` dpdklab
2024-08-14 10:45 ` dpdklab
2024-08-14 10:45 ` dpdklab
2024-08-14 10:48 ` dpdklab
2024-08-14 10:50 ` dpdklab
2024-08-14 10:51 ` dpdklab
2024-08-14 10:51 ` dpdklab
2024-08-14 10:52 ` dpdklab
2024-08-14 10:52 ` dpdklab
2024-08-14 10:53 ` dpdklab
2024-08-14 10:53 ` dpdklab
2024-08-14 10:54 ` dpdklab
2024-08-14 10:54 ` dpdklab
2024-08-14 10:55 ` dpdklab
2024-08-14 10:55 ` dpdklab
2024-08-14 10:56 ` dpdklab
2024-08-14 10:56 ` dpdklab
2024-08-14 10:57 ` dpdklab
2024-08-14 10:58 ` dpdklab
2024-08-14 10:59 ` dpdklab
2024-08-14 11:01 ` dpdklab
2024-08-14 11:01 ` dpdklab
2024-08-14 11:02 ` dpdklab
2024-08-14 11:03 ` dpdklab
2024-08-14 11:05 ` dpdklab
2024-08-14 11:08 ` dpdklab
2024-08-14 11:12 ` dpdklab
2024-08-14 11:13 ` dpdklab
2024-08-14 11:13 ` dpdklab
2024-08-14 11:16 ` dpdklab
2024-08-14 11:19 ` dpdklab
2024-08-14 11:19 ` dpdklab
2024-08-14 11:20 ` dpdklab
2024-08-14 11:22 ` dpdklab
2024-08-14 11:24 ` dpdklab
2024-08-14 11:24 ` dpdklab
2024-08-14 11:25 ` dpdklab
2024-08-14 11:26 ` |SUCCESS| " dpdklab
2024-08-14 11:26 ` |PENDING| " dpdklab
2024-08-14 11:27 ` dpdklab
2024-08-14 11:29 ` dpdklab
2024-08-14 11:30 ` dpdklab
2024-08-14 11:31 ` dpdklab
2024-08-14 11:32 ` dpdklab
2024-08-14 11:34 ` dpdklab
2024-08-14 11:34 ` dpdklab
2024-08-14 11:35 ` dpdklab
2024-08-14 11:36 ` dpdklab
2024-08-14 11:37 ` dpdklab
2024-08-14 11:38 ` dpdklab
2024-08-14 11:40 ` dpdklab
2024-08-14 11:40 ` |SUCCESS| " dpdklab
2024-08-14 11:41 ` dpdklab
2024-08-14 11:41 ` dpdklab
2024-08-14 11:42 ` |PENDING| " dpdklab
2024-08-14 11:42 ` |SUCCESS| " dpdklab
2024-08-14 11:42 ` dpdklab
2024-08-14 11:43 ` |PENDING| " dpdklab
2024-08-14 12:01 ` dpdklab
2024-08-14 12:02 ` dpdklab
2024-08-14 12:02 ` dpdklab
2024-08-14 12:04 ` dpdklab
2024-08-14 12:29 ` dpdklab
2024-08-14 12:44 ` dpdklab
2024-08-14 12:47 ` dpdklab
2024-08-14 13:16 ` |SUCCESS| " 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=20240814075214.ACC22123EFA@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=bruce.richards@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).