linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, yuehaibing@huawei.com
Subject: RE: [v2,-next] Bluetooth: Remove unused declaration amp_read_loc_info()
Date: Wed, 26 Jul 2023 19:20:14 -0700 (PDT)	[thread overview]
Message-ID: <64c1d45e.050a0220.f52f6.03e8@mx.google.com> (raw)
In-Reply-To: <20230727013907.29068-1-yuehaibing@huawei.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      0.82 seconds
GitLint                       FAIL      0.52 seconds
SubjectPrefix                 PASS      0.12 seconds
BuildKernel                   PASS      32.63 seconds
CheckAllWarning               PASS      35.23 seconds
CheckSparse                   PASS      39.91 seconds
CheckSmatch                   PASS      112.17 seconds
BuildKernel32                 PASS      30.89 seconds
TestRunnerSetup               PASS      469.75 seconds
TestRunner_l2cap-tester       PASS      21.85 seconds
TestRunner_iso-tester         PASS      40.19 seconds
TestRunner_bnep-tester        PASS      9.92 seconds
TestRunner_mgmt-tester        PASS      210.41 seconds
TestRunner_rfcomm-tester      PASS      15.05 seconds
TestRunner_sco-tester         PASS      15.97 seconds
TestRunner_ioctl-tester       PASS      16.89 seconds
TestRunner_mesh-tester        PASS      12.52 seconds
TestRunner_smp-tester         PASS      13.38 seconds
TestRunner_userchan-tester    PASS      10.43 seconds
IncrementalBuild              PASS      29.12 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v2,-next] Bluetooth: Remove unused declaration amp_read_loc_info()
WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#52: 
This is introduced in commit 903e45411099 ("Bluetooth: AMP: Use HCI cmd to Read Loc AMP Assoc")

total: 0 errors, 1 warnings, 0 checks, 7 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/13328661.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
Desc: Run gitlint
Output:
[v2,-next] Bluetooth: Remove unused declaration amp_read_loc_info()

WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
3: B1 Line exceeds max length (95>80): "This is introduced in commit 903e45411099 ("Bluetooth: AMP: Use HCI cmd to Read Loc AMP Assoc")"
4: B2 Line has trailing whitespace: "and never be implemented. "


---
Regards,
Linux Bluetooth


  reply	other threads:[~2023-07-27  2:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-27  1:39 [PATCH v2 -next] Bluetooth: Remove unused declaration amp_read_loc_info() Yue Haibing
2023-07-27  2:20 ` bluez.test.bot [this message]
2023-07-27 22:21 ` Luiz Augusto von Dentz
2023-07-28  3:29   ` YueHaibing

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=64c1d45e.050a0220.f52f6.03e8@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=yuehaibing@huawei.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).