From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, hj.tedd.an@gmail.com
Subject: RE: [BlueZ] shared: Fix the incorrect type with bit shift
Date: Thu, 17 Feb 2022 00:00:15 -0800 (PST) [thread overview]
Message-ID: <620e008f.1c69fb81.e8e70.8a3f@mx.google.com> (raw)
In-Reply-To: <20220217063145.50497-1-hj.tedd.an@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1316 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=615253
---Test result---
Test Summary:
CheckPatch PASS 0.52 seconds
GitLint FAIL 0.37 seconds
Prep - Setup ELL PASS 49.17 seconds
Build - Prep PASS 0.59 seconds
Build - Configure PASS 9.06 seconds
Build - Make PASS 1702.34 seconds
Make Check PASS 12.60 seconds
Make Check w/Valgrind PASS 502.72 seconds
Make Distcheck PASS 259.75 seconds
Build w/ext ELL - Configure PASS 9.78 seconds
Build w/ext ELL - Make PASS 1660.32 seconds
Incremental Build with patchesPASS 0.00 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint with rule in .gitlint
Output:
[BlueZ] shared: Fix the incorrect type with bit shift
9: B1 Line exceeds max length (114>80): " src/shared/btsnoop.c:339:18: runtime error: left shift of 65535 by 16 places cannot be represented in type 'int'"
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2022-02-17 8:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 6:31 [BlueZ PATCH] shared: Fix the incorrect type with bit shift Tedd Ho-Jeong An
2022-02-17 8:00 ` bluez.test.bot [this message]
2022-02-17 9:55 ` Marcel Holtmann
2022-02-17 16:36 ` Tedd Ho-Jeong An
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=620e008f.1c69fb81.e8e70.8a3f@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=hj.tedd.an@gmail.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 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.