Linux bluetooth development
 help / color / mirror / Atom feed
From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, michal.lowas-rzechonek@silvair.com
Subject: RE: [RFC,BlueZ] mesh: Allow calls to Attach/Leave before replying to JoinComplete
Date: Tue, 16 Jun 2020 03:07:54 -0700 (PDT)	[thread overview]
Message-ID: <5ee899fa.1c69fb81.4fec7.95e9@mx.google.com> (raw)
In-Reply-To: <20200616094009.21753-1-michal.lowas-rzechonek@silvair.com>

[-- Attachment #1: Type: text/plain, Size: 1333 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.
While we are preparing for reviewing the patches, we found the following
issue/warning.

Test Result:
checkpatch Failed

Outputs:
WARNING:LINE_SPACING: Missing a blank line after declarations
#107: FILE: mesh/mesh.c:466:
+	struct call_data *pending_call = l_new(struct call_data, 1);
+	pending_call->node = node;

WARNING:LINE_SPACING: Missing a blank line after declarations
#157: FILE: mesh/mesh.c:704:
+		struct mesh_node *node = node_find_by_token(token);
+		queue_pending_call(node, attach_call, msg, user_data);

ERROR:OPEN_BRACE: that open brace { should be on the previous line
#170: FILE: mesh/mesh.c:726:
+	if (!node_remove(node))
+	{

- total: 1 errors, 2 warnings, 269 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.

Your patch 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

NOTE: If any of the errors are false positives, please report
      them to the maintainer, see CHECKPATCH in MAINTAINERS.



---
Regards,
Linux Bluetooth

  reply	other threads:[~2020-06-16 10:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16  9:40 [RFC BlueZ] mesh: Allow calls to Attach/Leave before replying to JoinComplete Michał Lowas-Rzechonek
2020-06-16 10:07 ` bluez.test.bot [this message]
2020-06-16 10:10 ` [RFC,BlueZ] " 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=5ee899fa.1c69fb81.4fec7.95e9@mx.google.com \
    --to=bluez.test.bot@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=michal.lowas-rzechonek@silvair.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox