public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Alok <develnewbie@gmail.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [HFP][Patch] Plugin.
Date: Wed, 27 Feb 2008 19:38:30 +0530	[thread overview]
Message-ID: <1204121310.25999.17.camel@greatbear> (raw)
In-Reply-To: <20080227134910.GA26414@localhost>

Hi Johan, 

Find my responses inline. 

On Wed, 2008-02-27 at 15:49 +0200, Johan Hedberg wrote:
> Hi Alok,
> 
> Some comments below.
> 
> On Wed, Feb 27, 2008, Alok wrote:
> > +	AC_ARG_ENABLE(plugin, AC_HELP_STRING([--enable-plugin], [enable telephony plugins]), [
> > +		plugin_enable=${enableval}
> > +	])
> > +
> 
> Maybe --enable-hfp-plugin would be better since it's not clear what
> plugin is in question.
> 
sure. "--enable-hfp-plugin" sounds fine. 

> > +if PLUGIN
> > +plugindir = $(libdir)/bluetooth
> > +
> > +plugin_LTLIBRARIES = hfp_plugin_test.la
> > +
> > +hfp_plugin_test_la_SOURCES = hfp_plugin_test.c hfp_plugin.h
> > +hfp_plugin_test_la_LDFLAGS = -module
> > +hfp_plugin_test_la_LIBADD = @GLIB_LIBS@
> > +hfp_plugin_test_la_CFLAGS = @GLIB_CFLAGS@
> > +endif
> 
> Isn't there rist that these files get left out of "make dist" if you
> didn't give --enable-plugin to configure?
> 
I am not sure I understand. Is there some rule missing or something?
 
> > +int load_hfp_plugin(GKeyFile *config)
> > +{
> > +	gchar *str = NULL;
> > +	GError *err = NULL;
> > +	char filename[PATH_MAX];
> > +
> > +        str = g_key_file_get_string(config, "Headset", "Plugin", &err);
> 
> Incorrect indentation and missing check for config == NULL

Will fix that. 

> 
> > +	if (load_hfp_plugin(config) < 0)
> > +		return -1;
> 
> 
> I think we should keep the current policy that the audio service gets
> run successfully with some sane set of defaults if there is no audio.conf
> present in the filesystem. This change looks like it will make the audio
> service fail either if audio.conf doesn't exist or if it doesn't contain
> a Plugin entry.
> 
As far as I remember, Marcel had commented that there should not be a
default plugin. (in case of no audio.conf). But I am open to the idea.
We can have the test plugin as the default plugin. 

> > --- audio/unix.c	8 Feb 2008 17:43:48 -0000	1.64
> > +++ audio/unix.c	26 Feb 2008 15:19:44 -0000
> > @@ -36,10 +36,11 @@
> >  
> >  #include <bluetooth/bluetooth.h>
> >  #include <bluetooth/sdp.h>
> >  #include <dbus/dbus.h>
> >  #include <glib.h>
> > +#include <gmodule.h>

> Why do you need to add this include since there are no other changes to
> this file in your patch?
> 
You are right. This is unnecessary. will remove it. 
 
> Johan
> 

Thanks,
Alok.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2008-02-27 14:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-27 12:14 [Bluez-devel] [HFP][Patch] Plugin Alok
2008-02-27 13:49 ` Johan Hedberg
2008-02-27 14:08   ` Alok [this message]
2008-02-27 15:05   ` Alok

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=1204121310.25999.17.camel@greatbear \
    --to=develnewbie@gmail.com \
    --cc=bluez-devel@lists.sourceforge.net \
    /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