From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [DBUS PATCH] BondingCreated && BondingFailed
Date: Mon, 20 Feb 2006 15:10:17 +0100 [thread overview]
Message-ID: <1140444617.7047.21.camel@localhost> (raw)
In-Reply-To: <e1effdeb0602200558l7946fa17ubdb3042e5014dc9e@mail.gmail.com>
Hi Claudio,
> > signal = status ? DEV_SIG_BONDING_CREATED : DEV_SIG_BONDING_FAILED;
> >
> > and then call it with dbus_message_new_signal(..., signal).
> >
> > This end up in cleaner code and is easier to understand later.
>
> Modification done!
and patch is applied to the CVS.
> > > The next step is start the development of the missing bonding
> > > services: RemoveBonding, HasBonding and ListBonding.
> >
> > The textfile library should have all stuff for it all ready. So it
> > should be really easy to add.
>
> I've never checked the textfile functions. I will try understand the
> implemented functions and send you new patches soon.
Take a look at the GetAlias function. This will give you a nice example
on how easy this will be.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2006-02-20 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 18:07 [Bluez-devel] [DBUS PATCH] BondingCreated && BondingFailed Claudio Takahasi
2006-02-17 18:46 ` Marcel Holtmann
2006-02-20 13:58 ` Claudio Takahasi
2006-02-20 14:10 ` 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=1140444617.7047.21.camel@localhost \
--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;
as well as URLs for NNTP newsgroup(s).