From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, zhiyuan.sheng@oss.qualcomm.com
Subject: RE: [v1] obexd: fix PBAP PullPhoneBook failure with ebook backend
Date: Fri, 22 May 2026 01:51:59 -0700 (PDT) [thread overview]
Message-ID: <6a10192f.12ee227d.3179dd.95d0@mx.google.com> (raw)
In-Reply-To: <20260522060312.1503481-1-zhiyuan.sheng@oss.qualcomm.com>
[-- Attachment #1: Type: text/plain, Size: 826 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=1099150
---Test result---
Test Summary:
CheckPatch PASS 0.49 seconds
GitLint PASS 0.34 seconds
BuildEll PASS 20.38 seconds
BluezMake PASS 679.47 seconds
CheckSmatch PASS 362.36 seconds
bluezmakeextell PASS 187.61 seconds
IncrementalBuild PASS 668.91 seconds
ScanBuild PASS 1076.15 seconds
https://github.com/bluez/bluez/pull/2145
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-05-22 8:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 6:03 [PATCH v1] obexd: fix PBAP PullPhoneBook failure with ebook backend Zhiyuan Sheng
2026-05-22 8:51 ` bluez.test.bot [this message]
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=6a10192f.12ee227d.3179dd.95d0@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=zhiyuan.sheng@oss.qualcomm.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