From: "Brad Midgley" <bmidgley@gmail.com>
To: "BlueZ development" <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] newapi patch v1
Date: Fri, 19 Oct 2007 17:35:04 -0600 [thread overview]
Message-ID: <d89ddf300710191635v1c9c6c84pcd6b82d0affcefab@mail.gmail.com> (raw)
In-Reply-To: <4718E8E0.5050608@silicom.fr>
Fabien
> All, here is the first version of the patch that moves to the newapi
> usage... yeheee !!
This is all stuff we definitely need. Johan and Luiz have been working
more closely with this so I will leave it up to them to
comment/commit.
> As nobody suggested a new name, i've just chose one, which is
> "btaudioservice.h" :-). Of course this can be changed if somebody
> prefers a better name :-)
maybe audioclient.h. something like that would mesh best if it was
ever made officially externally available (ie
/usr/include/bluetooth/audioclient.h)
brad
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-10-19 23:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 17:26 [PATCH] newapi patch v1 Fabien Chevalier
2007-10-19 17:30 ` [Bluez-devel] " Fabien Chevalier
2007-10-19 17:30 ` Fabien Chevalier
2007-10-19 23:35 ` Brad Midgley [this message]
2007-10-23 18:01 ` Fabien Chevalier
2007-10-23 18:28 ` Marcel Holtmann
2007-10-24 12:12 ` Fabien Chevalier
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=d89ddf300710191635v1c9c6c84pcd6b82d0affcefab@mail.gmail.com \
--to=bmidgley@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