From: Johan Hedberg <johan.hedberg@intel.com>
To: Loic Poulain <loic.poulain@intel.com>
Cc: marcel@holtmann.org, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCHv6] tools: add bcm43xx specific init in hciattach
Date: Fri, 4 Apr 2014 10:38:39 +0300 [thread overview]
Message-ID: <20140404073839.GD16753@t440s.lan> (raw)
In-Reply-To: <1396515889-1270-1-git-send-email-loic.poulain@intel.com>
Hi Loic,
On Thu, Apr 03, 2014, Loic Poulain wrote:
> From: lpoulain <loic.poulain@intel.com>
You need to fix your git author information before this goes upstream.
The above should say "First Last <email>".
> Add a bcm43xx specific init sequence in hciattach
> in order to initialize bcm43xx controllers.
> ---
> v6: Coding style
>
> Makefile.tools | 3 +-
> tools/hciattach.c | 11 +-
> tools/hciattach.h | 2 +
> tools/hciattach_bcm43xx.c | 374 ++++++++++++++++++++++++++++++++++++++++++++++
> 4 files changed, 388 insertions(+), 2 deletions(-)
> create mode 100644 tools/hciattach_bcm43xx.c
The code looks fine now but doesn't actually compile:
CC tools/hciattach_bcm43xx.o
tools/hciattach_bcm43xx.c: In function ‘bcm43xx_read_local_name’:
tools/hciattach_bcm43xx.c:90:2: error: implicit declaration of function ‘free’ [-Werror=implicit-function-declaration]
free(resp);
^
tools/hciattach_bcm43xx.c:90:2: error: incompatible implicit declaration of built-in function ‘free’ [-Werror]
cc1: all warnings being treated as errors
make[1]: *** [tools/hciattach_bcm43xx.o] Error 1
I believe that's because you've forgotten to #include <stdlib.h> which
is needed by free().
Always compile test with ./bootstrap-configure && make
Johan
prev parent reply other threads:[~2014-04-04 7:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 9:04 [PATCHv6] tools: add bcm43xx specific init in hciattach Loic Poulain
2014-04-04 7:38 ` Johan Hedberg [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=20140404073839.GD16753@t440s.lan \
--to=johan.hedberg@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=loic.poulain@intel.com \
--cc=marcel@holtmann.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).