From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [DBUS-PATCH] list registered paths
Date: Fri, 14 Oct 2005 14:42:17 +0200 [thread overview]
Message-ID: <1129293738.5057.61.camel@localhost.localdomain> (raw)
In-Reply-To: <e1effdeb0510140530l6055351ak7505758983378586@mail.gmail.com>
Hi Claudio,
> The attached patch implements the service for list the registered
> paths under the path /org/bluez/Manager.
>
> The message request signature can be:
> 1. ListPaths() - list all paths under /org/bluez/Manager
> 2. ListPaths(String), The string is the relative path. eg: "hci0",
> "default" - list all paths provided by one adapter
do we really need this?
> Other minor changes:
> - removed some logs
> - added verification for dbus_connection_list_registered function. It
> can return FALSE if there is no memory
> to allocate the child entries
Don't send combined patches. If you have cleanups then send them as a
separate patch.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-10-14 12:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-14 12:30 [Bluez-devel] [DBUS-PATCH] list registered paths Claudio Takahasi
2005-10-14 12:42 ` Marcel Holtmann [this message]
2005-10-14 13:49 ` Claudio Takahasi
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=1129293738.5057.61.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--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