From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [BlueZ] test-runner: Add option to start emulator
Date: Wed, 2 Mar 2022 15:22:22 -0800 [thread overview]
Message-ID: <CABBYNZLBZQSaV1ckEzYXTjyqwpEFLLXdPUSiy73V_J05z0qmBw@mail.gmail.com> (raw)
In-Reply-To: <621d6a3a.1c69fb81.cfda5.a0ab@mx.google.com>
Hi,
On Mon, Feb 28, 2022 at 4:35 PM <bluez.test.bot@gmail.com> wrote:
>
> 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=618913
>
> ---Test result---
>
> Test Summary:
> CheckPatch FAIL 1.54 seconds
> GitLint PASS 1.05 seconds
> Prep - Setup ELL PASS 43.02 seconds
> Build - Prep PASS 0.74 seconds
> Build - Configure PASS 8.82 seconds
> Build - Make PASS 1440.03 seconds
> Make Check PASS 11.46 seconds
> Make Check w/Valgrind PASS 446.11 seconds
> Make Distcheck PASS 231.77 seconds
> Build w/ext ELL - Configure PASS 8.81 seconds
> Build w/ext ELL - Make PASS 1433.12 seconds
> Incremental Build with patchesPASS 0.00 seconds
>
> Details
> ##############################
> Test: CheckPatch - FAIL
> Desc: Run checkpatch.pl script with rule in .checkpatch.conf
> Output:
> [BlueZ] test-runner: Add option to start emulator
> ERROR:INITIALISED_STATIC: do not initialise statics to false
> #98: FILE: tools/test-runner.c:50:
> +static bool start_emulator = false;
>
> WARNING:STATIC_CONST_CHAR_ARRAY: static const char * array should probably be static const char * const
> #119: FILE: tools/test-runner.c:605:
> +static const char *btvirt_table[] = {
>
> /github/workspace/src/12763863.patch total: 1 errors, 1 warnings, 152 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.
>
> /github/workspace/src/12763863.patch has style problems, please review.
>
> NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPDX_LICENSE_TAG SPLIT_STRING SSCANF_TO_KSTRTO
>
> NOTE: If any of the errors are false positives, please report
> them to the maintainer, see CHECKPATCH in MAINTAINERS.
>
>
>
>
> ---
> Regards,
> Linux Bluetooth
>
Pushed.
--
Luiz Augusto von Dentz
prev parent reply other threads:[~2022-03-02 23:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 23:27 [PATCH BlueZ] test-runner: Add option to start emulator Luiz Augusto von Dentz
2022-03-01 0:35 ` [BlueZ] " bluez.test.bot
2022-03-02 23:22 ` Luiz Augusto von Dentz [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=CABBYNZLBZQSaV1ckEzYXTjyqwpEFLLXdPUSiy73V_J05z0qmBw@mail.gmail.com \
--to=luiz.dentz@gmail.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.