linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Cc: hj.tedd.an@gmail.com
Subject: Re: [BlueZ,v4,1/2] tools/bluemoon: Display FW version of firmware file
Date: Wed, 3 Feb 2021 11:08:56 -0800	[thread overview]
Message-ID: <CABBYNZLybQhs1Atm1KfUk7+OMxKv=z9hLTL3WFzCddDEWcNp=A@mail.gmail.com> (raw)
In-Reply-To: <6018d01f.1c69fb81.45e86.488c@mx.google.com>

Hi Tedd,

On Mon, Feb 1, 2021 at 8:14 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=425781
>
> ---Test result---
>
> ##############################
> Test: CheckPatch - FAIL
> Output:
> tools/bluemoon: Add support for checking other firmware file types
> WARNING:PREFER_DEFINED_ATTRIBUTE_MACRO: Prefer __packed over __attribute__((packed))
> #59: FILE: tools/bluemoon.c:757:
> +} __attribute__ ((packed));
>
> - total: 0 errors, 1 warnings, 168 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] tools/bluemoon: Add support for checking other firmware file" 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

Applied, thanks.

-- 
Luiz Augusto von Dentz

      reply	other threads:[~2021-02-03 19:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-02  3:40 [PATCH BlueZ v4 1/2] tools/bluemoon: Display FW version of firmware file Tedd Ho-Jeong An
2021-02-02  3:40 ` [PATCH BlueZ v4 2/2] tools/bluemoon: Add support for checking other firmware file types Tedd Ho-Jeong An
2021-02-02  4:07 ` [BlueZ,v4,1/2] tools/bluemoon: Display FW version of firmware file bluez.test.bot
2021-02-03 19:08   ` 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='CABBYNZLybQhs1Atm1KfUk7+OMxKv=z9hLTL3WFzCddDEWcNp=A@mail.gmail.com' \
    --to=luiz.dentz@gmail.com \
    --cc=hj.tedd.an@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 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).