All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [BlueZ,1/2] sdpd: Fix leaking buffers stored in cstates cache
Date: Fri, 12 Nov 2021 14:38:23 -0800 (PST)	[thread overview]
Message-ID: <618eecdf.1c69fb81.dd4d3.7201@mx.google.com> (raw)
In-Reply-To: <20211112220538.310085-1-luiz.dentz@gmail.com>

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

---Test result---

Test Summary:
CheckPatch                    FAIL      1.25 seconds
GitLint                       PASS      0.64 seconds
Prep - Setup ELL              PASS      51.41 seconds
Build - Prep                  PASS      0.24 seconds
Build - Configure             PASS      9.30 seconds
Build - Make                  PASS      218.48 seconds
Make Check                    PASS      9.70 seconds
Make Distcheck                PASS      262.91 seconds
Build w/ext ELL - Configure   PASS      9.61 seconds
Build w/ext ELL - Make        PASS      209.93 seconds

Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script with rule in .checkpatch.conf
Output:
[BlueZ,1/2] sdpd: Fix leaking buffers stored in cstates cache
WARNING:NEW_TYPEDEFS: do not add new typedefs
#110: FILE: src/sdpd-request.c:45:
+typedef struct sdp_cont_info sdp_cont_info_t;

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

[BlueZ,2/2] shared/gatt-server: Fix heap overflow when appending prepare writes
WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#89: 
Fixes https://github.com/bluez/bluez/security/advisories/GHSA-479m-xcq5-9g2q

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


  parent reply	other threads:[~2021-11-12 22:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-12 22:05 [PATCH BlueZ 1/2] sdpd: Fix leaking buffers stored in cstates cache Luiz Augusto von Dentz
2021-11-12 22:05 ` [PATCH BlueZ 2/2] shared/gatt-server: Fix heap overflow when appending prepare writes Luiz Augusto von Dentz
2021-11-12 22:38 ` bluez.test.bot [this message]
2021-11-15 20:05   ` [BlueZ,1/2] sdpd: Fix leaking buffers stored in cstates cache 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=618eecdf.1c69fb81.dd4d3.7201@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 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.