From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, roman.gushchin@linux.dev
Subject: RE: [net] 6lowpan: fix netdev_priv() type confusion in lowpan_event()
Date: Fri, 06 Nov 2026 18:29:40 -0800 (PST) [thread overview]
Message-ID: <6aee8d14.4001fe38.37437.e453@mx.google.com> (raw)
In-Reply-To: <20261106225930.1379968-1-roman.gushchin@linux.dev>
[-- Attachment #1: Type: text/plain, Size: 1781 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/series/1204595/
---Test result---
Test Summary:
CheckPatch PASS 3.26 seconds
VerifyFixes PASS 0.13 seconds
VerifySignedoff PASS 0.90 seconds
GitLint PASS 0.34 seconds
SubjectPrefix FAIL 0.18 seconds
BuildKernel PASS 31.03 seconds
CheckAllWarning PASS 35.02 seconds
CheckSparse PASS 39.77 seconds
BuildKernel32 PASS 31.26 seconds
CheckKernelLLVM PASS 35.89 seconds
TestRunnerSetup PASS 748.50 seconds
TestRunner_l2cap-tester PASS 12.85 seconds
TestRunner_iso-tester PASS 11.04 seconds
TestRunner_bnep-tester PASS 4.13 seconds
TestRunner_mgmt-tester PASS 89.48 seconds
TestRunner_rfcomm-tester PASS 8.33 seconds
TestRunner_sco-tester PASS 5.80 seconds
TestRunner_ioctl-tester PASS 4.76 seconds
TestRunner_mesh-tester PASS 5.59 seconds
TestRunner_smp-tester PASS 4.44 seconds
TestRunner_userchan-tester PASS 3.30 seconds
TestRunner_6lowpan-tester PASS 4.55 seconds
IncrementalBuild PASS 28.41 seconds
Details
##############################
Test: SubjectPrefix - FAIL
Desc: Check subject contains "Bluetooth" prefix
Output:
"Bluetooth: " prefix is not specified in the subject
https://github.com/bluez/bluetooth-next/pull/1083
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-11-07 2:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 22:59 [PATCH net] 6lowpan: fix netdev_priv() type confusion in lowpan_event() Roman Gushchin
2026-11-06 23:02 ` netdev-bot+sinfo
2026-11-06 23:10 ` Roman Gushchin
2026-11-06 23:50 ` Eric Dumazet
2026-11-07 2:29 ` 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=6aee8d14.4001fe38.37437.e453@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=roman.gushchin@linux.dev \
/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