From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, inga.stotland@intel.com
Subject: RE: [BlueZ,v5,10/10] mesh: Refactor heartbeat pub/sub
Date: Thu, 06 Aug 2020 20:49:28 -0700 (PDT) [thread overview]
Message-ID: <5f2ccf48.1c69fb81.6d7c3.7937@mx.google.com> (raw)
In-Reply-To: <20200807013834.123263-11-inga.stotland@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1002 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:UNNECESSARY_INT: Prefer 'long' over 'long int' as the int is unnecessary
#88: FILE: mesh/cfgmod-server.c:485:
+ if (time_now.tv_sec >= (long int) sub->period)
- total: 0 errors, 1 warnings, 784 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 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
next prev parent reply other threads:[~2020-08-07 3:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 1:38 [PATCH BlueZ v5 00/10] Mesh Config Server clean up Inga Stotland
2020-08-07 1:38 ` [PATCH BlueZ v5 01/10] mesh: Clean up handling of config subscription messages Inga Stotland
2020-08-07 3:49 ` [BlueZ,v5,01/10] " bluez.test.bot
2020-08-07 1:38 ` [PATCH BlueZ v5 02/10] mesh: Clean up handling of config model binding messages Inga Stotland
2020-08-07 1:38 ` [PATCH BlueZ v5 03/10] mesh: Clean up handling of config node identity message Inga Stotland
2020-08-07 1:38 ` [PATCH BlueZ v5 04/10] mesh: Clean up handling of config publication messages Inga Stotland
2020-08-07 1:38 ` [PATCH BlueZ v5 05/10] mesh: Clean up handling of config net and app key messages Inga Stotland
2020-08-07 3:49 ` [BlueZ,v5,05/10] " bluez.test.bot
2020-08-07 1:38 ` [PATCH BlueZ v5 06/10] mesh: Clean up handling of config relay messages Inga Stotland
2020-08-07 1:38 ` [PATCH BlueZ v5 07/10] mesh: Clean up handling of config poll timeout message Inga Stotland
2020-08-07 1:38 ` [PATCH BlueZ v5 08/10] mesh: Clean up handling of config net transmit messages Inga Stotland
2020-08-07 1:38 ` [PATCH BlueZ v5 09/10] mesh: Clean up handling of config KR phase messages Inga Stotland
2020-08-07 1:38 ` [PATCH BlueZ v5 10/10] mesh: Refactor heartbeat pub/sub Inga Stotland
2020-08-07 3:49 ` bluez.test.bot [this message]
2020-11-17 12:25 ` Steve Brown
2020-08-10 21:49 ` [PATCH BlueZ v5 00/10] Mesh Config Server clean up Gix, Brian
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=5f2ccf48.1c69fb81.6d7c3.7937@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 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).