From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, 515672508@qq.com
Subject: RE: [BlueZ] adapt:Set property mode failed,memory leak This patch will fix a memory leak,when set property mode,it will send a msg, but if failed,the data'memory do not free
Date: Fri, 14 Aug 2020 03:28:49 -0700 (PDT) [thread overview]
Message-ID: <5f366761.1c69fb81.53a96.12c8@mx.google.com> (raw)
In-Reply-To: <20200814095433.10654-1-515672508@qq.com>
[-- Attachment #1: Type: text/plain, Size: 1162 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:
checkbuild Failed
Outputs:
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
ar: `u' modifier ignored since `D' is the default (see `U')
src/adapter.c: In function ‘property_set_mode’:
src/adapter.c:2919:2: error: this ‘if’ clause does not guard... [-Werror=misleading-indentation]
2919 | if (mgmt_send(adapter->mgmt, opcode, adapter->dev_id, len, param,
| ^~
src/adapter.c:2922:3: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’
2922 | return;
| ^~~~~~
cc1: all warnings being treated as errors
make[1]: *** [Makefile:9167: src/bluetoothd-adapter.o] Error 1
make: *** [Makefile:4010: all] Error 2
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2020-08-14 10:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 9:54 [PATCH BlueZ] adapt:Set property mode failed,memory leak This patch will fix a memory leak,when set property mode,it will send a msg, but if failed,the data'memory do not free chengbo
2020-08-14 10:26 ` [BlueZ] " bluez.test.bot
2020-08-14 10:28 ` bluez.test.bot [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=5f366761.1c69fb81.53a96.12c8@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=515672508@qq.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).