public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Zhao Forrest <forrest.zhao@gmail.com>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>,
	event <event.riga@gmail.com>
Subject: Re: [PATCH 0/4] HFP Gateway profile -- take 2
Date: Thu, 19 Feb 2009 19:33:48 +0100	[thread overview]
Message-ID: <1235068428.4640.10.camel@californication> (raw)
In-Reply-To: <ac8af0be0902190519v150905c9iea04a86835750c5c@mail.gmail.com>

Hi Forrest,

> Compared with last version the change is:
> 1 fix the bug that HFP AG can't initiate the service-level connection
> with HFP HF unit.
> 2 rebase the patch set against the BlueZ master
> 
> The patch set include the following 4 patches:
> 1 add the D-Bus interface definition for HFP Audio gateway
> 2 add the basic framework support for HFP Audio gateway
> 3 the main part for HFP Audio gateway
> 4  IPC integration part for HFP Audio gateway

before we go any further with this, please make sure the coding style is
fixed.

static GDBusSignalTable gateway_signals[] = {
       {NULL, NULL}
};

It has to be "{ NULL, NULL }" and there are multiple of these mistakes.

And second, did you actually compiled the code?

       GIOChannel *rfcomm = gw->rfcomm;

       if (!io_channel_write_all(rfcomm, data, count))
               return FALSE;

       gsize read = 0;
       gboolean got_ok = FALSE;

This will not compile since you have variable declarations after the
code and the latest changes with -Werror are clearly forbidding this and
also checking for it.

Regards

Marcel



      reply	other threads:[~2009-02-19 18:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-19 13:19 [PATCH 0/4] HFP Gateway profile -- take 2 Zhao Forrest
2009-02-19 18:33 ` Marcel Holtmann [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=1235068428.4640.10.camel@californication \
    --to=marcel@holtmann.org \
    --cc=event.riga@gmail.com \
    --cc=forrest.zhao@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