linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, wangyouwan@uniontech.com
Subject: RE: device: Fix not removing connected device
Date: Wed, 22 Jun 2022 23:22:30 -0700 (PDT)	[thread overview]
Message-ID: <62b406a6.1c69fb81.d81f0.813b@mx.google.com> (raw)
In-Reply-To: <20220623031300.11581-1-wangyouwan@uniontech.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      1.49 seconds
GitLint                       PASS      0.95 seconds
Prep - Setup ELL              PASS      41.48 seconds
Build - Prep                  PASS      0.68 seconds
Build - Configure             PASS      8.06 seconds
Build - Make                  PASS      1196.70 seconds
Make Check                    PASS      11.80 seconds
Make Check w/Valgrind         PASS      439.72 seconds
Make Distcheck                PASS      228.36 seconds
Build w/ext ELL - Configure   PASS      8.08 seconds
Build w/ext ELL - Make        PASS      1187.94 seconds
Incremental Build with patchesPASS      0.00 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
Output:
device: Fix not removing connected device
WARNING:LONG_LINE: line length of 91 exceeds 80 columns
#131: FILE: src/device.c:3076:
+void device_remove_connection(struct btd_device *device, uint8_t bdaddr_type, bool *remove)

/github/workspace/src/12891800.patch total: 0 errors, 1 warnings, 54 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/12891800.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.




---
Regards,
Linux Bluetooth


  reply	other threads:[~2022-06-23  6:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23  3:13 [PATCH] device: Fix not removing connected device Youwan Wang
2022-06-23  6:22 ` bluez.test.bot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-06-23  6:29 Youwan Wang
2022-06-23  8:08 ` bluez.test.bot
2022-06-23  1:44 [PATCH] " Youwan Wang
2022-06-23  3:14 ` 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=62b406a6.1c69fb81.d81f0.813b@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=wangyouwan@uniontech.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 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).