linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, francesco@dolcini.it
Subject: RE: [v2] treewide, serdev: change receive_buf() return type to size_t
Date: Fri, 02 Feb 2024 13:56:31 -0800 (PST)	[thread overview]
Message-ID: <65bd650f.170a0220.feebb.3ac9@mx.google.com> (raw)
In-Reply-To: <20240122180551.34429-1-francesco@dolcini.it>

[-- Attachment #1: Type: text/plain, Size: 4012 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=818742

---Test result---

Test Summary:
CheckPatch                    FAIL      4.12 seconds
GitLint                       FAIL      0.46 seconds
SubjectPrefix                 FAIL      0.37 seconds
BuildKernel                   PASS      27.70 seconds
CheckAllWarning               PASS      30.49 seconds
CheckSparse                   PASS      35.96 seconds
CheckSmatch                   PASS      99.61 seconds
BuildKernel32                 PASS      28.31 seconds
TestRunnerSetup               PASS      507.40 seconds
TestRunner_l2cap-tester       PASS      17.25 seconds
TestRunner_iso-tester         PASS      32.68 seconds
TestRunner_bnep-tester        PASS      4.78 seconds
TestRunner_mgmt-tester        FAIL      110.18 seconds
TestRunner_rfcomm-tester      PASS      7.36 seconds
TestRunner_sco-tester         PASS      11.18 seconds
TestRunner_ioctl-tester       PASS      7.89 seconds
TestRunner_mesh-tester        PASS      5.93 seconds
TestRunner_smp-tester         PASS      6.84 seconds
TestRunner_userchan-tester    PASS      4.99 seconds
IncrementalBuild              PASS      26.44 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v2] treewide, serdev: change receive_buf() return type to size_t
WARNING: function definition argument 'struct serdev_device *' should also have an identifier name
#425: FILE: include/linux/serdev.h:30:
+	size_t (*receive_buf)(struct serdev_device *, const u8 *, size_t);

WARNING: function definition argument 'const u8 *' should also have an identifier name
#425: FILE: include/linux/serdev.h:30:
+	size_t (*receive_buf)(struct serdev_device *, const u8 *, size_t);

WARNING: function definition argument 'size_t' should also have an identifier name
#425: FILE: include/linux/serdev.h:30:
+	size_t (*receive_buf)(struct serdev_device *, const u8 *, size_t);

total: 0 errors, 3 warnings, 215 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/13525933.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:
[v2] treewide, serdev: change receive_buf() return type to size_t

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
23: B1 Line exceeds max length (82>80): "Link: https://lore.kernel.org/all/087be419-ec6b-47ad-851a-5e1e3ea5cfcc@kernel.org/"
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 497, Passed: 486 (97.8%), Failed: 5, Not Run: 6

Failed Test Cases
Read Ext Controller Info 1                           Failed       0.082 seconds
Read Ext Controller Info 2                           Failed       0.094 seconds
Read Ext Controller Info 3                           Failed       0.088 seconds
Read Ext Controller Info 4                           Failed       0.085 seconds
Read Ext Controller Info 5                           Failed       0.101 seconds


---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2024-02-02 21:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 18:05 [PATCH v2] treewide, serdev: change receive_buf() return type to size_t Francesco Dolcini
2024-01-22 18:17 ` [v2] " bluez.test.bot
2024-01-24 11:38 ` [PATCH v2] " Ilpo Järvinen
2024-01-24 18:20 ` Rob Herring
2024-01-24 18:43 ` Maximilian Luz
2024-01-24 21:59 ` Alex Elder
2024-01-25  7:37 ` Johan Hovold
2024-01-25 10:42 ` Lee Jones
2024-02-02 21:56 ` bluez.test.bot [this message]
2024-03-25  1:54 ` patchwork-bot+chrome-platform
2024-03-25  2:13 ` patchwork-bot+chrome-platform

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=65bd650f.170a0220.feebb.3ac9@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=francesco@dolcini.it \
    --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).