From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, inga.stotland@intel.com
Subject: RE: Framework for non-interactive mesh test
Date: Fri, 05 Feb 2021 20:58:38 -0800 (PST) [thread overview]
Message-ID: <601e21fe.1c69fb81.2de1e.1841@mx.google.com> (raw)
In-Reply-To: <20210206044340.396467-2-inga.stotland@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2188 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=429183
---Test result---
##############################
Test: CheckPatch - FAIL
Output:
shared/tester: Create ell-based version of tester code
WARNING:PREFER_DEFINED_ATTRIBUTE_MACRO: Prefer __packed over __attribute__((packed))
#168: FILE: src/shared/tester-ell.c:120:
+} __attribute__((packed));
WARNING:PREFER_DEFINED_ATTRIBUTE_MACRO: Prefer __packed over __attribute__((packed))
#173: FILE: src/shared/tester-ell.c:125:
+} __attribute__((packed));
- total: 0 errors, 2 warnings, 913 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
"[PATCH] shared/tester: Create ell-based version of tester code" has style problems, please review.
NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPLIT_STRING SSCANF_TO_KSTRTO
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
mesh: Add unit test IO
WARNING:SPDX_LICENSE_TAG: Missing or malformed SPDX-License-Identifier tag in line 1
#665: FILE: mesh/mesh-io-unit.h:1:
+/*
- total: 0 errors, 1 warnings, 677 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
"[PATCH] mesh: Add unit test IO" has style problems, please review.
NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPLIT_STRING SSCANF_TO_KSTRTO
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
Test: CheckGitLint - PASS
##############################
Test: CheckBuild - PASS
##############################
Test: MakeCheck - PASS
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2021-02-06 5:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-06 4:43 [PATCH BlueZ v2 0/3] Framework for non-interactive mesh test Inga Stotland
2021-02-06 4:43 ` [PATCH BlueZ v2 1/3] shared/tester: Create ell-based version of tester code Inga Stotland
2021-02-06 4:58 ` bluez.test.bot [this message]
2021-02-06 4:43 ` [PATCH BlueZ v2 2/3] mesh: Add unit test IO Inga Stotland
2021-02-06 4:43 ` [PATCH BlueZ v2 3/3] tools/mesh-cfgtest: Non-iteractive test for mesh daemon Inga Stotland
-- strict thread matches above, loose matches on Subject: below --
2021-03-19 20:38 [PATCH BlueZ v4 1/2] mesh: Add unit test IO Inga Stotland
2021-03-19 20:53 ` Framework for non-interactive mesh test bluez.test.bot
2021-03-25 6:45 ` bluez.test.bot
2021-04-05 17:05 ` bluez.test.bot
2021-02-06 5:50 [PATCH BlueZ v3 1/3] shared/tester: Create ell-based version of tester code Inga Stotland
2021-02-06 6:36 ` Framework for non-interactive mesh test bluez.test.bot
2021-02-06 1:31 [PATCH BlueZ 1/3] shared/tester: Create ell-based version of tester code Inga Stotland
2021-02-06 3:35 ` Framework for non-interactive mesh test bluez.test.bot
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=601e21fe.1c69fb81.2de1e.1841@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=inga.stotland@intel.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 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.