linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, dan.carpenter@oracle.com
Subject: RE: Bluetooth: clean up error pointer checking
Date: Wed, 20 Jul 2022 05:02:45 -0700 (PDT)	[thread overview]
Message-ID: <62d7eee5.1c69fb81.98fe7.4b47@mx.google.com> (raw)
In-Reply-To: <YtflxRosxskh2CoH@kili>

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

---Test result---

Test Summary:
CheckPatch                    PASS      1.37 seconds
GitLint                       PASS      0.56 seconds
SubjectPrefix                 PASS      0.30 seconds
BuildKernel                   PASS      45.84 seconds
BuildKernel32                 PASS      40.97 seconds
Incremental Build with patchesPASS      69.34 seconds
TestRunner: Setup             PASS      676.66 seconds
TestRunner: l2cap-tester      PASS      19.85 seconds
TestRunner: bnep-tester       PASS      7.13 seconds
TestRunner: mgmt-tester       PASS      118.69 seconds
TestRunner: rfcomm-tester     PASS      11.35 seconds
TestRunner: sco-tester        PASS      11.69 seconds
TestRunner: smp-tester        PASS      11.14 seconds
TestRunner: userchan-tester   PASS      7.73 seconds



---
Regards,
Linux Bluetooth


  reply	other threads:[~2022-07-20 12:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-20 11:23 [PATCH] Bluetooth: clean up error pointer checking Dan Carpenter
2022-07-20 12:02 ` bluez.test.bot [this message]
2022-07-20 16:20 ` 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=62d7eee5.1c69fb81.98fe7.4b47@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=dan.carpenter@oracle.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 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).