From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, andriy.shevchenko@linux.intel.com
Subject: RE: [v1,1/1] Bluetooth: MGMT: Use correct address for memcpy()
Date: Mon, 17 Jul 2023 03:00:53 -0700 (PDT) [thread overview]
Message-ID: <64b51155.0c0a0220.8e13e.49be@mx.google.com> (raw)
In-Reply-To: <20230717093214.82102-1-andriy.shevchenko@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2970 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=766403
---Test result---
Test Summary:
CheckPatch FAIL 1.00 seconds
GitLint FAIL 0.63 seconds
SubjectPrefix PASS 0.12 seconds
BuildKernel PASS 33.07 seconds
CheckAllWarning PASS 36.51 seconds
CheckSparse PASS 41.89 seconds
CheckSmatch PASS 111.84 seconds
BuildKernel32 PASS 32.10 seconds
TestRunnerSetup PASS 486.10 seconds
TestRunner_l2cap-tester PASS 23.37 seconds
TestRunner_iso-tester PASS 44.64 seconds
TestRunner_bnep-tester PASS 10.67 seconds
TestRunner_mgmt-tester PASS 219.00 seconds
TestRunner_rfcomm-tester PASS 16.00 seconds
TestRunner_sco-tester PASS 17.03 seconds
TestRunner_ioctl-tester PASS 18.09 seconds
TestRunner_mesh-tester PASS 13.41 seconds
TestRunner_smp-tester PASS 14.44 seconds
TestRunner_userchan-tester PASS 11.17 seconds
IncrementalBuild PASS 30.70 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v1,1/1] Bluetooth: MGMT: Use correct address for memcpy()
WARNING: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#70:
inlined from ‘get_conn_info_complete’ at net/bluetooth/mgmt.c:7281:2:
total: 0 errors, 1 warnings, 0 checks, 8 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/13315359.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.
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
[v1,1/1] Bluetooth: MGMT: Use correct address for memcpy()
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 (217>80): "include/linux/fortify-string.h:592:25: error: call to ‘__read_overflow2_field’ declared with attribute warning: detected read beyond size of field (2nd parameter); maybe use struct_group()? [-Werror=attribute-warning]"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-07-17 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 9:32 [PATCH v1 1/1] Bluetooth: MGMT: Use correct address for memcpy() Andy Shevchenko
2023-07-17 10:00 ` bluez.test.bot [this message]
2023-07-17 20:00 ` 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=64b51155.0c0a0220.8e13e.49be@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=andriy.shevchenko@linux.intel.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 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.