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, william.xuanziyang@huawei.com
Subject: RE: Bluetooth: Remove unnecessary NULL check before vfree()
Date: Sun, 06 Aug 2023 20:16:44 -0700 (PDT)	[thread overview]
Message-ID: <64d0621c.4a0a0220.943bf.091a@mx.google.com> (raw)
In-Reply-To: <20230807023206.2128846-1-william.xuanziyang@huawei.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      0.71 seconds
GitLint                       FAIL      0.56 seconds
SubjectPrefix                 PASS      0.10 seconds
BuildKernel                   PASS      43.73 seconds
CheckAllWarning               PASS      46.79 seconds
CheckSparse                   PASS      54.08 seconds
CheckSmatch                   PASS      145.77 seconds
BuildKernel32                 PASS      41.48 seconds
TestRunnerSetup               PASS      641.68 seconds
TestRunner_l2cap-tester       PASS      31.51 seconds
TestRunner_iso-tester         PASS      85.57 seconds
TestRunner_bnep-tester        PASS      14.37 seconds
TestRunner_mgmt-tester        FAIL      257.97 seconds
TestRunner_rfcomm-tester      PASS      21.70 seconds
TestRunner_sco-tester         PASS      24.16 seconds
TestRunner_ioctl-tester       PASS      24.67 seconds
TestRunner_mesh-tester        PASS      18.26 seconds
TestRunner_smp-tester         PASS      19.38 seconds
TestRunner_userchan-tester    PASS      15.55 seconds
IncrementalBuild              PASS      39.32 seconds

Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
Bluetooth: Remove unnecessary NULL check before vfree()

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
4: B1 Line exceeds max length (98>80): "net/bluetooth/coredump.c:104:2-7: WARNING: NULL check before some freeing functions is not needed."
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 497, Passed: 496 (99.8%), Failed: 1, Not Run: 0

Failed Test Cases
LL Privacy - Unpair 1                                Timed out    2.067 seconds


---
Regards,
Linux Bluetooth


  reply	other threads:[~2023-08-07  3:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07  2:32 [PATCH] Bluetooth: Remove unnecessary NULL check before vfree() Ziyang Xuan
2023-08-07  3:16 ` bluez.test.bot [this message]
2023-08-07 22:50 ` 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=64d0621c.4a0a0220.943bf.091a@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=william.xuanziyang@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