public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, surban@surban.net
Subject: RE: [BlueZ] gatt-server: Flush notify multiple buffer when full and fix overflow
Date: Fri, 11 Jun 2021 01:42:06 -0700 (PDT)	[thread overview]
Message-ID: <60c321de.1c69fb81.635b0.db01@mx.google.com> (raw)
In-Reply-To: <20210611081932.4279-1-surban@surban.net>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      0.31 seconds
GitLint                       PASS      0.11 seconds
Prep - Setup ELL              PASS      44.15 seconds
Build - Prep                  PASS      0.10 seconds
Build - Configure             PASS      7.14 seconds
Build - Make                  PASS      189.01 seconds
Make Check                    PASS      9.48 seconds
Make Distcheck                PASS      207.31 seconds
Build w/ext ELL - Configure   PASS      6.78 seconds
Build w/ext ELL - Make        PASS      157.09 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
Output:
gatt-server: Flush notify multiple buffer when full and fix overflow
WARNING:LONG_LINE_COMMENT: line length of 81 exceeds 80 columns
#28: FILE: src/shared/gatt-server.c:1706:
+		/* Flush buffered data, if this request hits buffer size limit */

WARNING:LONG_LINE: line length of 88 exceeds 80 columns
#29: FILE: src/shared/gatt-server.c:1707:
+		if (data && data->offset > 0 && data->len - data->offset < 4 + length) {

- total: 0 errors, 2 warnings, 38 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] gatt-server: Flush notify multiple buffer when full and fix" 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 - PASS
Desc: Run gitlint with rule in .gitlint

##############################
Test: Prep - Setup ELL - PASS
Desc: Clone, build, and install ELL

##############################
Test: Build - Prep - PASS
Desc: Prepare environment for build

##############################
Test: Build - Configure - PASS
Desc: Configure the BlueZ source tree

##############################
Test: Build - Make - PASS
Desc: Build the BlueZ source tree

##############################
Test: Make Check - PASS
Desc: Run 'make check'

##############################
Test: Make Distcheck - PASS
Desc: Run distcheck to check the distribution

##############################
Test: Build w/ext ELL - Configure - PASS
Desc: Configure BlueZ source with '--enable-external-ell' configuration

##############################
Test: Build w/ext ELL - Make - PASS
Desc: Build BlueZ source with '--enable-external-ell' configuration



---
Regards,
Linux Bluetooth


  reply	other threads:[~2021-06-11  8:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-11  8:19 [PATCH BlueZ] gatt-server: Flush notify multiple buffer when full and fix overflow Sebastian Urban
2021-06-11  8:42 ` bluez.test.bot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-06-11 12:29 Sebastian Urban
2021-06-11 12:52 ` [BlueZ] " bluez.test.bot
2021-06-12  9:32 [PATCH BlueZ] " Sebastian Urban
2021-06-12  9:56 ` [BlueZ] " bluez.test.bot
2021-06-13 10:39 [PATCH BlueZ] " Sebastian Urban
2021-06-13 11:04 ` [BlueZ] " bluez.test.bot
2021-06-14 21:06   ` Luiz Augusto von Dentz

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=60c321de.1c69fb81.635b0.db01@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=surban@surban.net \
    /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