public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hdegoede@redhat.com
Subject: RE: Bluetooth: hci_event: Fix vendor (unknown) opcode status handling
Date: Sun, 07 Aug 2022 14:59:01 -0700 (PDT)	[thread overview]
Message-ID: <62f035a5.050a0220.aebd4.50b5@mx.google.com> (raw)
In-Reply-To: <20220807205740.777363-1-hdegoede@redhat.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      1.88 seconds
GitLint                       PASS      1.09 seconds
SubjectPrefix                 PASS      0.84 seconds
BuildKernel                   PASS      33.71 seconds
BuildKernel32                 PASS      29.15 seconds
Incremental Build with patchesPASS      40.88 seconds
TestRunner: Setup             PASS      486.89 seconds
TestRunner: l2cap-tester      PASS      17.54 seconds
TestRunner: bnep-tester       PASS      6.73 seconds
TestRunner: mgmt-tester       PASS      104.38 seconds
TestRunner: rfcomm-tester     PASS      10.12 seconds
TestRunner: sco-tester        PASS      9.90 seconds
TestRunner: smp-tester        PASS      9.92 seconds
TestRunner: userchan-tester   PASS      7.00 seconds

Details
##############################
Test: CheckPatch - FAIL - 1.88 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
Bluetooth: hci_event: Fix vendor (unknown) opcode status handling\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)")'
#68: 
Commit c8992cffbe74 ("Bluetooth: hci_event: Use of a function table to
handle Command Complete") was (presumably) meant to only refactor things

total: 1 errors, 0 warnings, 0 checks, 13 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/12938271.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.




---
Regards,
Linux Bluetooth


  reply	other threads:[~2022-08-07 22:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-07 20:57 [PATCH] Bluetooth: hci_event: Fix vendor (unknown) opcode status handling Hans de Goede
2022-08-07 21:59 ` bluez.test.bot [this message]
2022-08-08  7:50   ` Hans de Goede
2022-08-08 19:58 ` [PATCH] " Luiz Augusto von Dentz
2022-08-10 22:26   ` Luiz Augusto von Dentz
2022-08-11 11:52     ` Hans de Goede

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=62f035a5.050a0220.aebd4.50b5@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=hdegoede@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox