From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, trix@redhat.com
Subject: RE: Bluetooth: btmtk: fix handling of CONFIG_DEV_COREDUMP not being defined
Date: Sun, 02 Jul 2023 13:57:01 -0700 (PDT) [thread overview]
Message-ID: <64a1e49d.c80a0220.5befe.92b6@mx.google.com> (raw)
In-Reply-To: <20230702202603.3442724-1-trix@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2074 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=761864
---Test result---
Test Summary:
CheckPatch PASS 0.67 seconds
GitLint FAIL 0.57 seconds
SubjectPrefix PASS 0.11 seconds
BuildKernel PASS 32.07 seconds
CheckAllWarning PASS 34.90 seconds
CheckSparse PASS 39.39 seconds
CheckSmatch PASS 110.87 seconds
BuildKernel32 PASS 30.47 seconds
TestRunnerSetup PASS 440.12 seconds
TestRunner_l2cap-tester PASS 12.85 seconds
TestRunner_iso-tester PASS 23.62 seconds
TestRunner_bnep-tester PASS 5.48 seconds
TestRunner_mgmt-tester PASS 129.83 seconds
TestRunner_rfcomm-tester PASS 8.95 seconds
TestRunner_sco-tester PASS 10.41 seconds
TestRunner_ioctl-tester PASS 9.70 seconds
TestRunner_mesh-tester PASS 7.01 seconds
TestRunner_smp-tester PASS 8.15 seconds
TestRunner_userchan-tester PASS 5.81 seconds
IncrementalBuild PASS 28.73 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
Bluetooth: btmtk: fix handling of CONFIG_DEV_COREDUMP not being defined
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
5: B1 Line exceeds max length (84>80): "drivers/bluetooth/btmtk.c:386:44: error: ‘struct hci_dev’ has no member named ‘dump’"
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2023-07-02 20:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 20:26 [PATCH] Bluetooth: btmtk: fix handling of CONFIG_DEV_COREDUMP not being defined Tom Rix
2023-07-02 20:26 ` Tom Rix
2023-07-02 20:57 ` 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=64a1e49d.c80a0220.5befe.92b6@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=trix@redhat.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.