public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, pengpeng@iscas.ac.cn
Subject: RE: [v2] Bluetooth: RFCOMM: pull credit byte with skb_pull_data()
Date: Thu, 23 Apr 2026 16:29:44 -0700 (PDT)	[thread overview]
Message-ID: <69eaab68.050a0220.94ee0.9fda@mx.google.com> (raw)
In-Reply-To: <20260424070102.1-rfcomm-v2-pengpeng@iscas.ac.cn>

[-- Attachment #1: Type: text/plain, Size: 935 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=1084930

---Test result---

Test Summary:
CheckPatch                    PASS      0.52 seconds
GitLint                       PASS      0.23 seconds
SubjectPrefix                 PASS      0.09 seconds
BuildKernel                   PASS      21.35 seconds
CheckAllWarning               PASS      23.64 seconds
CheckSparse                   PASS      23.81 seconds
BuildKernel32                 PASS      20.22 seconds
TestRunnerSetup               PASS      415.26 seconds
TestRunner_rfcomm-tester      PASS      7.45 seconds
IncrementalBuild              PASS      20.39 seconds



https://github.com/bluez/bluetooth-next/pull/118

---
Regards,
Linux Bluetooth


  reply	other threads:[~2026-04-23 23:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-17  7:34 [PATCH] Bluetooth: RFCOMM: require a credit byte before consuming it Pengpeng Hou
2026-04-17  8:36 ` bluez.test.bot
2026-04-22 15:15 ` [PATCH] " Luiz Augusto von Dentz
2026-04-23 15:31 ` [PATCH v2] Bluetooth: RFCOMM: pull credit byte with skb_pull_data() Pengpeng Hou
2026-04-23 23:29   ` bluez.test.bot [this message]
2026-04-24 18:50   ` 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=69eaab68.050a0220.94ee0.9fda@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=pengpeng@iscas.ac.cn \
    /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