Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,v1,1/3] tools/tester: Fix crash when hciemu_new fails
Date: Wed, 06 May 2026 14:12:34 -0700 (PDT)	[thread overview]
Message-ID: <69fbaec2.050a0220.b3c4a.10f6@mx.google.com> (raw)
In-Reply-To: <20260506194150.1701855-1-luiz.dentz@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      1.10 seconds
GitLint                       PASS      0.74 seconds
BuildEll                      PASS      20.80 seconds
BluezMake                     PASS      652.47 seconds
CheckSmatch                   WARNING   352.56 seconds
bluezmakeextell               PASS      184.99 seconds
IncrementalBuild              PASS      680.38 seconds
ScanBuild                     PASS      1001.16 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[BlueZ,v1,3/3] tools/tester: Retry with debug on hciemu_new failure
WARNING:LONG_LINE: line length of 81 exceeds 80 columns
#241: FILE: tools/sco-tester.c:196:
+		data->hciemu = hciemu_new_debug(HCIEMU_TYPE_BREDRLE, print_debug,

/github/workspace/src/patch/14557929.patch total: 0 errors, 1 warnings, 100 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/patch/14557929.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: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
tools/sco-tester.c: note: in included file:./lib/bluetooth/bluetooth.h:232:15: warning: array of flexible structures./lib/bluetooth/bluetooth.h:237:31: warning: array of flexible structurestools/sco-tester.c: note: in included file:./lib/bluetooth/bluetooth.h:232:15: warning: array of flexible structures./lib/bluetooth/bluetooth.h:237:31: warning: array of flexible structures


https://github.com/bluez/bluez/pull/2103

---
Regards,
Linux Bluetooth


  parent reply	other threads:[~2026-05-06 21:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-06 19:41 [PATCH BlueZ v1 1/3] tools/tester: Fix crash when hciemu_new fails Luiz Augusto von Dentz
2026-05-06 19:41 ` [PATCH BlueZ v1 2/3] emulator/hciemu: Add hciemu_new_debug/hciemu_new_num_debug Luiz Augusto von Dentz
2026-05-06 19:41 ` [PATCH BlueZ v1 3/3] tools/tester: Retry with debug on hciemu_new failure Luiz Augusto von Dentz
2026-05-06 21:12 ` bluez.test.bot [this message]
2026-05-07 16:10 ` [PATCH BlueZ v1 1/3] tools/tester: Fix crash when hciemu_new fails 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=69fbaec2.050a0220.b3c4a.10f6@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox