All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, ismael@iodev.co.uk
Subject: RE: [v3] Replace the usage of non-standard GNU-basename with strrchr
Date: Thu, 19 Sep 2024 06:58:46 -0700 (PDT)	[thread overview]
Message-ID: <66ec2e16.170a0220.98932.081f@mx.google.com> (raw)
In-Reply-To: <20240919120252.25086-2-ismael@iodev.co.uk>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      0.59 seconds
GitLint                       FAIL      0.47 seconds
BuildEll                      PASS      25.70 seconds
BluezMake                     PASS      1722.67 seconds
MakeCheck                     PASS      12.84 seconds
MakeDistcheck                 PASS      192.27 seconds
CheckValgrind                 PASS      266.30 seconds
CheckSmatch                   WARNING   368.16 seconds
bluezmakeextell               PASS      120.80 seconds
IncrementalBuild              PASS      1505.35 seconds
ScanBuild                     PASS      1041.61 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v3] Replace the usage of non-standard GNU-basename with strrchr
ERROR:TRAILING_WHITESPACE: trailing whitespace
#103: FILE: tools/hex2hcd.c:307:
+^I^I$

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

NOTE: Whitespace errors detected.
      You may wish to use scripts/cleanpatch or scripts/cleanfile

/github/workspace/src/src/13807662.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:
[v3] Replace the usage of non-standard GNU-basename with strrchr

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
12: B2 Line has trailing whitespace: "    "
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
tools/hex2hcd.c:136:26: warning: Variable length array is used.


---
Regards,
Linux Bluetooth


      reply	other threads:[~2024-09-19 13:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19 12:02 [PATCH v3] Replace the usage of non-standard GNU-basename with strrchr Ismael Luceno
2024-09-19 13:58 ` bluez.test.bot [this message]

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=66ec2e16.170a0220.98932.081f@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=ismael@iodev.co.uk \
    --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 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.