All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, max.chou@realtek.com
Subject: RE: [v2] Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C
Date: Fri, 04 Aug 2023 04:42:29 -0700 (PDT)	[thread overview]
Message-ID: <64cce425.620a0220.d372.31da@mx.google.com> (raw)
In-Reply-To: <20230804104735.9281-1-max.chou@realtek.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      1.07 seconds
GitLint                       PASS      0.27 seconds
SubjectPrefix                 PASS      0.07 seconds
BuildKernel                   PASS      46.44 seconds
CheckAllWarning               PASS      50.56 seconds
CheckSparse                   PASS      56.03 seconds
CheckSmatch                   PASS      150.02 seconds
BuildKernel32                 PASS      44.31 seconds
TestRunnerSetup               PASS      676.10 seconds
TestRunner_l2cap-tester       PASS      34.63 seconds
TestRunner_iso-tester         PASS      91.63 seconds
TestRunner_bnep-tester        PASS      15.60 seconds
TestRunner_mgmt-tester        PASS      280.65 seconds
TestRunner_rfcomm-tester      PASS      23.38 seconds
TestRunner_sco-tester         PASS      23.01 seconds
TestRunner_ioctl-tester       PASS      26.18 seconds
TestRunner_mesh-tester        PASS      19.82 seconds
TestRunner_smp-tester         PASS      20.83 seconds
TestRunner_userchan-tester    PASS      16.29 seconds
IncrementalBuild              PASS      41.38 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v2] Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C
WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#89: 
The previous FW format of RTL8852C is v1. After the commit[2], the FW format

WARNING: Please use correct Fixes: style 'Fixes: <12 chars of sha1> ("<title line>")' - ie: 'Fixes:  ("Bluetooth: btrtl: Firmware format v2 support")'
#107: 
Fixes: 9a24ce5e29b ("Bluetooth: btrtl: Firmware format v2 support")

total: 0 errors, 2 warnings, 224 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/src/13341662.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.


Use of uninitialized value $cid in concatenation (.) or string at /github/workspace/src/src/scripts/checkpatch.pl line 3226.


---
Regards,
Linux Bluetooth


      parent reply	other threads:[~2023-08-04 11:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-04 10:47 [PATCH v2] Bluetooth: btrtl: Load FW v2 otherwise FW v1 for RTL8852C max.chou
2023-08-04 10:57 ` kernel test robot
2023-08-04 11:42 ` bluez.test.bot [this message]

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=64cce425.620a0220.d372.31da@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=max.chou@realtek.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 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.