All of lore.kernel.org
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, quic_zijuhu@quicinc.com
Subject: RE: [v2] Bluetooth: Devcoredump: Fix storing u32 without specifying byte order issue
Date: Mon, 17 Apr 2023 03:34:13 -0700 (PDT)	[thread overview]
Message-ID: <643d20a5.c80a0220.db65b.e98a@mx.google.com> (raw)
In-Reply-To: <1681724399-28292-1-git-send-email-quic_zijuhu@quicinc.com>

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

---Test result---

Test Summary:
CheckPatch                    PASS      0.71 seconds
GitLint                       PASS      0.34 seconds
SubjectPrefix                 PASS      0.13 seconds
BuildKernel                   PASS      31.81 seconds
CheckAllWarning               PASS      34.90 seconds
CheckSparse                   PASS      40.02 seconds
CheckSmatch                   PASS      109.25 seconds
BuildKernel32                 PASS      31.11 seconds
TestRunnerSetup               PASS      440.77 seconds
TestRunner_l2cap-tester       PASS      16.90 seconds
TestRunner_iso-tester         PASS      20.85 seconds
TestRunner_bnep-tester        PASS      5.56 seconds
TestRunner_mgmt-tester        PASS      114.94 seconds
TestRunner_rfcomm-tester      PASS      8.84 seconds
TestRunner_sco-tester         PASS      8.21 seconds
TestRunner_ioctl-tester       PASS      9.58 seconds
TestRunner_mesh-tester        PASS      6.94 seconds
TestRunner_smp-tester         PASS      8.07 seconds
TestRunner_userchan-tester    PASS      5.81 seconds
IncrementalBuild              PASS      29.67 seconds



---
Regards,
Linux Bluetooth


  reply	other threads:[~2023-04-17 10:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11 11:49 [PATCH v1] Bluetooth: Optimize devcoredump API hci_devcd_init() Zijun Hu
2023-04-11 12:41 ` [v1] " bluez.test.bot
2023-04-14 21:03 ` [PATCH v1] " Luiz Augusto von Dentz
2023-04-17  9:39 ` [PATCH v2] Bluetooth: Devcoredump: Fix storing u32 without specifying byte order issue Zijun Hu
2023-04-17 10:34   ` bluez.test.bot [this message]
2023-04-17 18:30   ` patchwork-bot+bluetooth
2023-04-17 18:30 ` [PATCH v1] Bluetooth: Optimize devcoredump API hci_devcd_init() 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=643d20a5.c80a0220.db65b.e98a@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=quic_zijuhu@quicinc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.