From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [PATCH] Better D-BUS path tracking
Date: Wed, 02 Nov 2005 19:47:40 +0100 [thread overview]
Message-ID: <1130957260.5442.14.camel@localhost.localdomain> (raw)
In-Reply-To: <20051102183915.GA13523@localhost.localdomain>
Hi Johan,
> > > This patch introduces a new path_id field to the hci_dbus_data struct as
> > > well as renames the id field to dev_id. This allows more accurate path
> > > identification in the callback functions. It also removes the need to do
> > > hard-to-follow string manipulations to find out the child path component.
> >
> > the patch is in the CVS now.
>
> The patch contained by mistake also the authenticate patch I sent earlier.
> After applying it the code calls twice dbus_message_new_method_return. Sorry
> about that. Here's a patch to fix it.
is in the CVS now.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-11-02 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 15:32 [Bluez-devel] [PATCH] Better D-BUS path tracking Johan Hedberg
2005-11-02 16:17 ` Marcel Holtmann
2005-11-02 18:40 ` Johan Hedberg
2005-11-02 18:47 ` 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=1130957260.5442.14.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