From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pavelm@google.com
Subject: RE: Fix duplicate free for GATT service includes
Date: Thu, 19 Nov 2020 14:31:03 -0800 (PST) [thread overview]
Message-ID: <5fb6f227.1c69fb81.e0c3d.64e1@mx.google.com> (raw)
In-Reply-To: <20201119214337.3886160-1-pavelm@google.com>
[-- Attachment #1: Type: text/plain, Size: 1822 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=387933
---Test result---
##############################
Test: CheckPatch - FAIL
Output:
Fix duplicate free for GATT service includes
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#14:
bluetoothd: src/gatt-database.c:gatt_db_service_removed() Local GATT service removed
- total: 0 errors, 1 warnings, 19 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.
"[PATCH] Fix duplicate free for GATT service includes" has style problems, please review.
NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPLIT_STRING SSCANF_TO_KSTRTO
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: CheckGitLint - FAIL
Output:
Fix duplicate free for GATT service includes
11: B1 Line exceeds max length (84>80): "bluetoothd: src/gatt-database.c:gatt_db_service_removed() Local GATT service removed"
14: B1 Line exceeds max length (94>80): "bluetoothd: src/sdpd-service.c:remove_record_from_server() Removing record with handle 0x10006"
15: B1 Line exceeds max length (94>80): "bluetoothd: src/gatt-database.c:proxy_removed_cb() Proxy removed - removing service: /service1"
##############################
Test: CheckBuild - PASS
##############################
Test: MakeCheck - PASS
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2020-11-19 22:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 21:43 [PATCH] Fix duplicate free for GATT service includes Pavel Maltsev
2020-11-19 22:31 ` bluez.test.bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-11-20 0:22 Pavel Maltsev
2020-11-20 1:00 ` bluez.test.bot
2020-11-20 17:48 ` Luiz Augusto von Dentz
2020-11-19 20:02 [PATCH] " Pavel Maltsev
2020-11-19 20:27 ` bluez.test.bot
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=5fb6f227.1c69fb81.e0c3d.64e1@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pavelm@google.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