From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, chris.lu@mediatek.com
Subject: RE: [v2] Bluetooth: btmtk: Fix null pointer when processing coredump
Date: Tue, 11 Jul 2023 21:39:21 -0700 (PDT) [thread overview]
Message-ID: <64ae2e79.050a0220.6992e.580a@mx.google.com> (raw)
In-Reply-To: <20230712034206.12484-1-chris.lu@mediatek.com>
[-- Attachment #1: Type: text/plain, Size: 2172 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=764635
---Test result---
Test Summary:
CheckPatch FAIL 0.98 seconds
GitLint PASS 0.34 seconds
SubjectPrefix PASS 0.13 seconds
BuildKernel PASS 33.41 seconds
CheckAllWarning PASS 37.07 seconds
CheckSparse PASS 41.83 seconds
CheckSmatch PASS 112.94 seconds
BuildKernel32 PASS 32.24 seconds
TestRunnerSetup PASS 494.86 seconds
TestRunner_l2cap-tester PASS 23.46 seconds
TestRunner_iso-tester PASS 42.33 seconds
TestRunner_bnep-tester PASS 10.63 seconds
TestRunner_mgmt-tester PASS 220.73 seconds
TestRunner_rfcomm-tester PASS 16.10 seconds
TestRunner_sco-tester PASS 17.10 seconds
TestRunner_ioctl-tester PASS 18.45 seconds
TestRunner_mesh-tester PASS 13.72 seconds
TestRunner_smp-tester PASS 14.62 seconds
TestRunner_userchan-tester PASS 11.37 seconds
IncrementalBuild PASS 30.90 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v2] Bluetooth: btmtk: Fix null pointer when processing coredump
WARNING: Co-developed-by: must be immediately followed by Signed-off-by:
#82:
Co-developed-by: Sean Wang <sean.wang@mediatek.com>
---
total: 0 errors, 1 warnings, 30 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/13309551.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
prev parent reply other threads:[~2023-07-12 4:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 3:42 [PATCH v2] Bluetooth: btmtk: Fix null pointer when processing coredump Chris Lu
2023-07-12 4:39 ` 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=64ae2e79.050a0220.6992e.580a@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=chris.lu@mediatek.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;
as well as URLs for NNTP newsgroup(s).