From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, bigeasy@linutronix.de
Subject: RE: net: Convert user to netif_rx(), part 3.
Date: Sun, 06 Mar 2022 15:00:11 -0800 (PST) [thread overview]
Message-ID: <62253cfb.1c69fb81.ad015.0f49@mx.google.com> (raw)
In-Reply-To: <20220306215753.3156276-7-bigeasy@linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 2440 bytes --]
This is automated email and please do not reply to this email!
Dear submitter,
Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=620752
---Test result---
Test Summary:
CheckPatch FAIL 1.03 seconds
GitLint FAIL 0.45 seconds
SubjectPrefix FAIL 0.32 seconds
BuildKernel PASS 33.53 seconds
BuildKernel32 PASS 29.85 seconds
Incremental Build with patchesPASS 39.86 seconds
TestRunner: Setup PASS 525.29 seconds
TestRunner: l2cap-tester PASS 16.50 seconds
TestRunner: bnep-tester PASS 6.45 seconds
TestRunner: mgmt-tester PASS 107.98 seconds
TestRunner: rfcomm-tester PASS 8.33 seconds
TestRunner: sco-tester PASS 8.05 seconds
TestRunner: smp-tester PASS 8.16 seconds
TestRunner: userchan-tester PASS 6.73 seconds
Details
##############################
Test: CheckPatch - FAIL - 1.03 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
[net-next,06/10] bluetooth: Use netif_rx().\WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#68:
baebdf48c3600 ("net: dev: Makes sure netif_rx() can be invoked in any context.")
total: 0 errors, 1 warnings, 0 checks, 16 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
/github/workspace/src/12770937.patch has style problems, please review.
NOTE: Ignored message types: UNKNOWN_COMMIT_ID
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: GitLint - FAIL - 0.45 seconds
Run gitlint with rule in .gitlint
[net-next,06/10] bluetooth: Use netif_rx().
1: T3 Title has trailing punctuation (.): "[net-next,06/10] bluetooth: Use netif_rx()."
4: B1 Line exceeds max length (83>80): " baebdf48c3600 ("net: dev: Makes sure netif_rx() can be invoked in any context.")"
##############################
Test: SubjectPrefix - FAIL - 0.32 seconds
Check subject contains "Bluetooth" prefix
"Bluetooth: " is not specified in the subject
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-03-06 23:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 21:57 [PATCH net-next 00/10] net: Convert user to netif_rx(), part 3 Sebastian Andrzej Siewior
2022-03-06 21:57 ` [PATCH net-next 01/10] s390: net: Use netif_rx() Sebastian Andrzej Siewior
2022-03-06 21:57 ` [PATCH net-next 02/10] staging: " Sebastian Andrzej Siewior
2022-03-06 22:12 ` Greg Kroah-Hartman
2022-03-06 21:57 ` [PATCH net-next 03/10] tun: vxlan: " Sebastian Andrzej Siewior
2022-03-06 21:57 ` [PATCH net-next 04/10] tipc: " Sebastian Andrzej Siewior
2022-03-06 21:57 ` [PATCH net-next 05/10] batman-adv: " Sebastian Andrzej Siewior
2022-03-07 7:26 ` Sven Eckelmann
2022-03-07 7:26 ` Sven Eckelmann
2022-03-06 21:57 ` [PATCH net-next 06/10] bluetooth: " Sebastian Andrzej Siewior
2022-03-06 23:00 ` bluez.test.bot [this message]
2022-03-06 21:57 ` [PATCH net-next 07/10] phonet: " Sebastian Andrzej Siewior
2022-03-07 15:58 ` Rémi Denis-Courmont
2022-03-06 21:57 ` [PATCH net-next 08/10] net: phy: micrel: " Sebastian Andrzej Siewior
2022-03-06 21:57 ` [PATCH net-next 09/10] net: Remove netif_rx_any_context() and netif_rx_ni() Sebastian Andrzej Siewior
2022-03-06 21:57 ` [PATCH net-next 10/10] net: phy: micrel: Move netif_rx() outside of IRQ-off section Sebastian Andrzej Siewior
2022-03-07 12:00 ` [PATCH net-next 00/10] net: Convert user to netif_rx(), part 3 patchwork-bot+netdevbpf
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=62253cfb.1c69fb81.ad015.0f49@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=linux-bluetooth@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.