From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, abhay.maheshbhai.maheta@intel.com
Subject: RE: Bug Fix for Memory overwrite
Date: Fri, 07 Oct 2022 08:44:09 -0700 (PDT) [thread overview]
Message-ID: <63404949.9d0a0220.c2cf9.4e47@mx.google.com> (raw)
In-Reply-To: <20221007145920.20966-2-abhay.maheshbhai.maheta@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1367 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=683730
---Test result---
Test Summary:
CheckPatch PASS 1.08 seconds
GitLint FAIL 0.80 seconds
Prep - Setup ELL PASS 31.61 seconds
Build - Prep PASS 0.92 seconds
Build - Configure PASS 10.17 seconds
Build - Make PASS 1137.58 seconds
Make Check PASS 12.56 seconds
Make Check w/Valgrind PASS 342.61 seconds
Make Distcheck PASS 281.81 seconds
Build w/ext ELL - Configure PASS 10.11 seconds
Build w/ext ELL - Make PASS 103.11 seconds
Incremental Build w/ patches PASS 0.00 seconds
Scan Build PASS 675.30 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint with rule in .gitlint
Output:
[BlueZ,1/1] shared/bap: Fix handling memory overwrite during ASE Enable Operation
1: T1 Title exceeds max length (81>80): "[BlueZ,1/1] shared/bap: Fix handling memory overwrite during ASE Enable Operation"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-10-07 15:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 14:59 [PATCH BlueZ 0/1] Bug Fix for Memory overwrite Abhay Maheta
2022-10-07 14:59 ` [PATCH BlueZ 1/1] shared/bap: Fix handling memory overwrite during ASE Enable Operation Abhay Maheta
2022-10-07 15:44 ` bluez.test.bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-07 17:45 Abhay Maheta
2022-10-07 18:22 ` Bug Fix for Memory overwrite 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=63404949.9d0a0220.c2cf9.4e47@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=abhay.maheshbhai.maheta@intel.com \
--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 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).