public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: event <event.riga@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Gateway profile
Date: Wed, 17 Dec 2008 03:48:53 +0100	[thread overview]
Message-ID: <1229482133.10889.5.camel@violet> (raw)
In-Reply-To: <664d43d60812151514m6c225403i528453fcb6f08430@mail.gmail.com>

Hi Leonid,

> I've implemented gateway profile. I've tested basic things, like
> place/cancel/answer call. Others are in development. Some could not be
> tested as my carrier doesn't provide corresponding services (like
> 3-way call, etc.) so any help welcome.

thanks for the works, but can you please base the patch against the
latest GIT tree. It is kinda hard to review things that might already
have been implemented like sco_listen.

 audio/audio-api.txt  |   94 +++++
 audio/device.h       |    7 
 audio/gateway.c      |  938 +++++++++++++++++++++++++++++++++++++++++++++++++++
 audio/gateway.h      |   11 
 audio/manager.c      |  124 ++++--
 common/glib-helper.c |   85 +++-
 common/glib-helper.h |    1 
 7 files changed, 1205 insertions(+), 55 deletions(-)

So any changes to glib-helper.[ch] have to be in a separate patch and
need to be discussed independent from the gateway implementation.

Any audio-api.txt stuff should also go separately since that has to be
discussed. Also we can't send PCM data over D-Bus. It just doesn't work
like that. We do have the internal IPC for that and plugins for ALSA,
GStreamer and PulseAudio that should be used.

However the most important part is that you follow the coding style and
that is the kernel coding style. You make it really hard for us to
review the code like this and it can't be applied. I really want you to
add support for the gateway role to BlueZ, but the overall code in the
project needs to follow the same rules.

So please fix these issues first and then we do a deep review of it.

Regards

Marcel



  reply	other threads:[~2008-12-17  2:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <664d43d60812151512y6631ebf2j9665e1473193077d@mail.gmail.com>
2008-12-15 23:14 ` [PATCH] Gateway profile event
2008-12-17  2:48   ` Marcel Holtmann [this message]
2008-12-19  7:36     ` event
2009-01-16 13:22     ` event
2009-01-18 16:07       ` Marcel Holtmann
2009-01-19  8:37         ` event
2009-01-19  9:20           ` Marcel Holtmann
2009-01-19 10:02             ` event
2009-01-19 10:11               ` Marcel Holtmann
2009-02-06 12:08 Thierry Pierret

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=1229482133.10889.5.camel@violet \
    --to=marcel@holtmann.org \
    --cc=event.riga@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