From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, vlad.pruteanu@nxp.com
Subject: RE: client/player: Fix transport.send command's transfer of packets
Date: Fri, 19 Apr 2024 09:40:29 -0700 (PDT) [thread overview]
Message-ID: <66229e7d.0c0a0220.31bc6.8617@mx.google.com> (raw)
In-Reply-To: <20240419145805.46263-2-vlad.pruteanu@nxp.com>
[-- Attachment #1: Type: text/plain, Size: 1279 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=846161
---Test result---
Test Summary:
CheckPatch PASS 0.41 seconds
GitLint PASS 0.26 seconds
BuildEll PASS 24.53 seconds
BluezMake PASS 1712.85 seconds
MakeCheck PASS 13.17 seconds
MakeDistcheck PASS 176.46 seconds
CheckValgrind PASS 250.02 seconds
CheckSmatch PASS 353.84 seconds
bluezmakeextell PASS 118.77 seconds
IncrementalBuild PASS 1478.60 seconds
ScanBuild WARNING 1002.10 seconds
Details
##############################
Test: ScanBuild - WARNING
Desc: Run Scan Build
Output:
client/player.c:4985:5: warning: Value stored to 'offset' is never read
offset = lseek(fd, -transport->mtu[1],
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 warning generated.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2024-04-19 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 14:58 [PATCH BlueZ v2 0/1] client/player: Fix transport.send command's transfer of packets Vlad Pruteanu
2024-04-19 14:58 ` [PATCH BlueZ v2 1/1] " Vlad Pruteanu
2024-04-19 15:24 ` Luiz Augusto von Dentz
2024-04-19 18:16 ` Luiz Augusto von Dentz
2024-04-20 12:42 ` Pauli Virtanen
2024-04-19 16:40 ` bluez.test.bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-25 14:40 [PATCH BlueZ " Vlad Pruteanu
2024-03-25 16:41 ` 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=66229e7d.0c0a0220.31bc6.8617@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=vlad.pruteanu@nxp.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 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).