automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Timothy Miskell <timothy.miskell@intel.com>
Subject: |WARNING| pw132987 [PATCH] ice: Increase L1 check interval to account for lengthier link time
Date: Thu, 19 Oct 2023 18:39:47 +0200 (CEST)	[thread overview]
Message-ID: <20231019163947.5E9CA120A1D@dpdk.org> (raw)
In-Reply-To: <20231019163846.324098-1-timothy.miskell@intel.com>

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

_coding style issues_


WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#64: 
For edge cases where the transceiver is physically inserted first and immediately afterwards the DPDK PF is started the LSC event may occur outside the current setting for the maximum check interval window. This change lengthens the check interval to account for this along with other reported cases where the link event be longer than 1 second.

ERROR:BAD_SIGN_OFF: Unrecognized email address: 'Timothy Miskell'
#68: 
Reported-by: Timothy Miskell

ERROR:BAD_SIGN_OFF: Unrecognized email address: 'Timothy Miskell'
#69: 
Suggested-by: Timothy Miskell

ERROR:BAD_SIGN_OFF: Unrecognized email address: 'Timothy Miskell'
#70: 
Signed-off-by: Timothy Miskell

ERROR:BAD_SIGN_OFF: Unrecognized email address: 'Larry Wang'
#71: 
Reviewed-by: Larry Wang

ERROR:BAD_SIGN_OFF: Unrecognized email address: 'Jonathan Tsai'
#72: 
Tested-by: Jonathan Tsai

ERROR:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch author 'Timothy Miskell <timothy.miskell@intel.com>'

total: 6 errors, 1 warnings, 0 checks, 24 lines checked

  parent reply	other threads:[~2023-10-19 16:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231019163846.324098-1-timothy.miskell@intel.com>
2023-10-19 16:21 ` |SUCCESS| " qemudev
2023-10-19 16:25 ` qemudev
2023-10-19 16:39 ` checkpatch [this message]
2023-10-19 17:59 ` 0-day Robot

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=20231019163947.5E9CA120A1D@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=test-report@dpdk.org \
    --cc=timothy.miskell@intel.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).