From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, wsa+renesas@sang-engineering.com
Subject: RE: Bluetooth: move from strlcpy with unused retval to strscpy
Date: Thu, 18 Aug 2022 15:01:12 -0700 (PDT) [thread overview]
Message-ID: <62feb6a8.c80a0220.d0075.5df0@mx.google.com> (raw)
In-Reply-To: <20220818210207.8323-1-wsa+renesas@sang-engineering.com>
[-- Attachment #1: Type: text/plain, Size: 1409 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=668973
---Test result---
Test Summary:
CheckPatch PASS 1.57 seconds
GitLint FAIL 0.97 seconds
SubjectPrefix PASS 0.85 seconds
BuildKernel PASS 33.52 seconds
BuildKernel32 PASS 29.27 seconds
Incremental Build with patchesPASS 42.62 seconds
TestRunner: Setup PASS 488.32 seconds
TestRunner: l2cap-tester PASS 17.56 seconds
TestRunner: bnep-tester PASS 6.84 seconds
TestRunner: mgmt-tester PASS 104.32 seconds
TestRunner: rfcomm-tester PASS 10.07 seconds
TestRunner: sco-tester PASS 9.98 seconds
TestRunner: smp-tester PASS 9.98 seconds
TestRunner: userchan-tester PASS 6.99 seconds
Details
##############################
Test: GitLint - FAIL - 0.97 seconds
Run gitlint with rule in .gitlint
Bluetooth: move from strlcpy with unused retval to strscpy
7: B1 Line exceeds max length (99>80): "Link: https://lore.kernel.org/r/CAHk-=wgfRnXz0W3D37d01q3JFkr_i_uTL=V6A6G1oUZcprmknw@mail.gmail.com/"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-08-18 22:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 21:02 [PATCH] Bluetooth: move from strlcpy with unused retval to strscpy Wolfram Sang
2022-08-18 22:01 ` bluez.test.bot [this message]
2022-08-18 22:07 ` Luiz Augusto von Dentz
2022-08-18 22:09 ` Randy Dunlap
2022-08-24 22:30 ` 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=62feb6a8.c80a0220.d0075.5df0@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.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.