From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, k.samburskiy@omp.ru
Subject: RE: obexd: Fix transfer status change
Date: Tue, 25 Nov 2025 02:35:25 -0800 (PST) [thread overview]
Message-ID: <6925866d.050a0220.336289.c23f@mx.google.com> (raw)
In-Reply-To: <20251125093835.17472-2-k.samburskiy@omp.ru>
[-- Attachment #1: Type: text/plain, Size: 1261 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=1027279
---Test result---
Test Summary:
CheckPatch PENDING 0.38 seconds
GitLint PENDING 0.32 seconds
BuildEll PASS 20.06 seconds
BluezMake PASS 630.43 seconds
MakeCheck PASS 21.64 seconds
MakeDistcheck PASS 238.55 seconds
CheckValgrind PASS 294.69 seconds
CheckSmatch PASS 342.73 seconds
bluezmakeextell PASS 181.58 seconds
IncrementalBuild PENDING 0.34 seconds
ScanBuild PASS 973.81 seconds
Details
##############################
Test: CheckPatch - PENDING
Desc: Run checkpatch.pl script
Output:
##############################
Test: GitLint - PENDING
Desc: Run gitlint
Output:
##############################
Test: IncrementalBuild - PENDING
Desc: Incremental build with the patches in the series
Output:
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2025-11-25 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 9:38 [PATCH BlueZ 0/1] obexd: Fix transfer status change Kirill Samburskiy
2025-11-25 9:38 ` [PATCH BlueZ 1/1] obexd: Always flush tranfser status changes. Set status to queued before starting Kirill Samburskiy
2025-11-25 10:35 ` bluez.test.bot [this message]
2025-11-26 16:40 ` [PATCH BlueZ 0/1] obexd: Fix transfer status change patchwork-bot+bluetooth
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=6925866d.050a0220.336289.c23f@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=k.samburskiy@omp.ru \
--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