All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, tot0roprog@gmail.com
Subject: RE: mesh: Fix segmentation behavior of Lower transport layer
Date: Mon, 14 Oct 2024 01:25:05 -0700 (PDT)	[thread overview]
Message-ID: <670cd561.0c0a0220.76a70.bcc4@mx.google.com> (raw)
In-Reply-To: <670caa89.a70a0220.5edfe.2cd5@mx.google.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      2.54 seconds
GitLint                       FAIL      1.68 seconds
BuildEll                      PASS      24.59 seconds
BluezMake                     PASS      1652.70 seconds
MakeCheck                     PASS      12.95 seconds
MakeDistcheck                 PASS      178.11 seconds
CheckValgrind                 PASS      252.05 seconds
CheckSmatch                   PASS      357.87 seconds
bluezmakeextell               PASS      120.03 seconds
IncrementalBuild              PASS      6218.53 seconds
ScanBuild                     PASS      1016.20 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v2,4/4] mesh: Add features of Segmented Control message
WARNING:LONG_LINE: line length of 83 exceeds 80 columns
#749: FILE: unit/test-mesh-crypto.c:1090:
+			seg_max = SEG_MAX(false, keys->segmented, app_msg_len + 8);

WARNING:LONG_LINE: line length of 83 exceeds 80 columns
#758: FILE: unit/test-mesh-crypto.c:1100:
+			seg_max = SEG_MAX(false, keys->segmented, app_msg_len + 4);

/github/workspace/src/src/13834162.patch total: 0 errors, 2 warnings, 602 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/13834162.patch has style problems, please review.

NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPDX_LICENSE_TAG 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: GitLint - FAIL
Desc: Run gitlint
Output:
[BlueZ,v2,1/4] mesh: Implement lower transport layer for segmentation and reassembly

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
1: T1 Title exceeds max length (84>80): "[BlueZ,v2,1/4] mesh: Implement lower transport layer for segmentation and reassembly"


---
Regards,
Linux Bluetooth


  reply	other threads:[~2024-10-14  8:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-14  5:22 [PATCH BlueZ v2 1/4] mesh: Implement lower transport layer for segmentation and reassembly Junho Lee
2024-10-14  8:25 ` bluez.test.bot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-14  7:54 [PATCH BlueZ v3 " Junho Lee
2024-10-14 11:09 ` mesh: Fix segmentation behavior of Lower transport layer bluez.test.bot
2024-11-11  7:39   ` Junho Lee
2024-10-04  7:31 [PATCH BlueZ 1/4] mesh: Implement lower transport layer for segmentation and reassembly Junho Lee
2024-10-04  8:57 ` mesh: Fix segmentation behavior of Lower transport layer 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=670cd561.0c0a0220.76a70.bcc4@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=tot0roprog@gmail.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.