linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, rahul@sandhuservices.dev
Subject: RE: tools/hex2hcd: fix musl compatibility
Date: Wed, 10 Jul 2024 07:17:31 -0700 (PDT)	[thread overview]
Message-ID: <668e97fb.050a0220.3132a.8a25@mx.google.com> (raw)
In-Reply-To: <20240710123002.5639-1-rahul@sandhuservices.dev>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      0.71 seconds
GitLint                       PASS      0.87 seconds
BuildEll                      PASS      24.82 seconds
BluezMake                     PASS      1589.95 seconds
MakeCheck                     PASS      13.30 seconds
MakeDistcheck                 PASS      178.09 seconds
CheckValgrind                 PASS      254.21 seconds
CheckSmatch                   WARNING   356.62 seconds
bluezmakeextell               PASS      120.00 seconds
IncrementalBuild              PASS      1372.16 seconds
ScanBuild                     PASS      1008.59 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
tools/hex2hcd: fix musl compatibility
ERROR:OPEN_BRACE: open brace '{' following function definitions go on the next line
#64: FILE: tools/hex2hcd.c:288:
+static const char *helper_basename(const char *path) {

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#65: FILE: tools/hex2hcd.c:289:
+  const char *base = strrchr(path, '/');$

WARNING:LINE_SPACING: Missing a blank line after declarations
#66: FILE: tools/hex2hcd.c:290:
+  const char *base = strrchr(path, '/');
+  return base ? base + 1 : path;

WARNING:LEADING_SPACE: please, no spaces at the start of a line
#66: FILE: tools/hex2hcd.c:290:
+  return base ? base + 1 : path;$

/github/workspace/src/src/13729245.patch total: 1 errors, 3 warnings, 19 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/13729245.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/hex2hcd.c:135:26: warning: Variable length array is used.


---
Regards,
Linux Bluetooth


      reply	other threads:[~2024-07-10 14:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-10 12:30 [PATCH] tools/hex2hcd: fix musl compatibility Rahul Sandhu
2024-07-10 14:17 ` 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=668e97fb.050a0220.3132a.8a25@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=rahul@sandhuservices.dev \
    /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).