linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: Bluetooth: core: Fix deadlock on hci_power_on_sync.
Date: Tue, 05 Jul 2022 11:20:25 -0700 (PDT)	[thread overview]
Message-ID: <62c480e9.1c69fb81.b96e9.2f1a@mx.google.com> (raw)
In-Reply-To: <20220705172501.1610923-1-luiz.dentz@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2593 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=656752

---Test result---

Test Summary:
CheckPatch                    FAIL      1.57 seconds
GitLint                       FAIL      0.78 seconds
SubjectPrefix                 PASS      0.80 seconds
BuildKernel                   PASS      31.82 seconds
BuildKernel32                 PASS      27.22 seconds
Incremental Build with patchesPASS      40.95 seconds
TestRunner: Setup             PASS      466.79 seconds
TestRunner: l2cap-tester      PASS      16.42 seconds
TestRunner: bnep-tester       PASS      5.59 seconds
TestRunner: mgmt-tester       PASS      95.09 seconds
TestRunner: rfcomm-tester     PASS      9.00 seconds
TestRunner: sco-tester        PASS      8.75 seconds
TestRunner: smp-tester        PASS      8.95 seconds
TestRunner: userchan-tester   PASS      5.74 seconds

Details
##############################
Test: CheckPatch - FAIL - 1.57 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
Bluetooth: core: Fix deadlock on hci_power_on_sync.\WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#108: 
[1]: commit dd06ed7ad057 ("Bluetooth: core: Fix missing power_on work cancel on HCI close")

ERROR:GIT_COMMIT_ID: Please use git commit description style 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit fatal: unsaf ("ace/src' is owned by someone else)")'
#108: 
[1]: commit dd06ed7ad057 ("Bluetooth: core: Fix missing power_on work cancel on HCI close")

total: 1 errors, 1 warnings, 0 checks, 22 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/12906901.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.78 seconds
Run gitlint with rule in .gitlint
Bluetooth: core: Fix deadlock on hci_power_on_sync.
1: T3 Title has trailing punctuation (.): "Bluetooth: core: Fix deadlock on hci_power_on_sync."
33: B1 Line exceeds max length (91>80): "[1]: commit dd06ed7ad057 ("Bluetooth: core: Fix missing power_on work cancel on HCI close")"




---
Regards,
Linux Bluetooth


  reply	other threads:[~2022-07-05 18:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-05 17:25 [PATCH] Bluetooth: core: Fix deadlock on hci_power_on_sync Luiz Augusto von Dentz
2022-07-05 18:20 ` bluez.test.bot [this message]
2022-07-05 18:30 ` patchwork-bot+bluetooth

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=62c480e9.1c69fb81.b96e9.2f1a@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.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).