From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, penguin-kernel@I-love.SAKURA.ne.jp
Subject: RE: Bluetooth: hci_sync: fix double mgmt_pending_free() in remove_adv_monitor()
Date: Wed, 17 Aug 2022 05:01:41 -0700 (PDT) [thread overview]
Message-ID: <62fcd8a5.050a0220.19ee9.1790@mx.google.com> (raw)
In-Reply-To: <ea64b27e-6cbf-fdd5-1f23-aecc3a308e47@I-love.SAKURA.ne.jp>
[-- Attachment #1: Type: text/plain, Size: 2069 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=668362
---Test result---
Test Summary:
CheckPatch FAIL 1.67 seconds
GitLint PASS 1.00 seconds
SubjectPrefix PASS 0.83 seconds
BuildKernel PASS 39.01 seconds
BuildKernel32 PASS 34.80 seconds
Incremental Build with patchesPASS 49.40 seconds
TestRunner: Setup PASS 559.58 seconds
TestRunner: l2cap-tester PASS 19.08 seconds
TestRunner: bnep-tester PASS 7.71 seconds
TestRunner: mgmt-tester PASS 115.23 seconds
TestRunner: rfcomm-tester PASS 11.41 seconds
TestRunner: sco-tester PASS 11.14 seconds
TestRunner: smp-tester PASS 11.07 seconds
TestRunner: userchan-tester PASS 7.90 seconds
Details
##############################
Test: CheckPatch - FAIL - 1.67 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
Bluetooth: hci_sync: fix double mgmt_pending_free() in remove_adv_monitor()\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)")'
#63:
commit 7cf5c2978f23fdbb ("Bluetooth: hci_sync: Refactor remove Adv
Monitor") forgot to remove duplicated mgmt_pending_remove() when
total: 1 errors, 0 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/12945738.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
next prev parent reply other threads:[~2022-08-17 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 10:42 [syzbot] KASAN: use-after-free Read in mgmt_pending_remove syzbot
2022-08-17 11:14 ` [PATCH] Bluetooth: hci_sync: fix double mgmt_pending_free() in remove_adv_monitor() Tetsuo Handa
2022-08-17 12:01 ` bluez.test.bot [this message]
2022-08-17 18:52 ` 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=62fcd8a5.050a0220.19ee9.1790@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/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