Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] [PATCH] dbus.c cleanup
Date: Tue, 01 Nov 2005 14:11:14 +0100	[thread overview]
Message-ID: <1130850674.31561.65.camel@blade> (raw)
In-Reply-To: <e1effdeb0510310547m51a457f2m19f00ec5cf194289@mail.gmail.com>

Hi Claudio,

> Probably in the future when we start develop another features(rfcomm,
> pan, ...) we will find more shared functions. I will put the find_conn
> to a lib.c(inside de hcid) directory first according with your
> suggestion. In the future we can discuss it later again.
> Another file that I want create is the error.c

send me a separate patch for the move to the lib.c file.

What do you wanna put into the error.c file. Explain me your idea behind
it and the benefits.

> When the dbus-daemon exits, the hcid will receive a "Disconnect"
> signal. The hcid can start a task to re-establish the bus connection
> each X seconds or it can exit.
> Currently, hcid catches the signal, but there is no action associated
> with this signal.

I see and it seems we need a patch to deal with the dbus-daemon exits in
case of restarts or errors in it. Please come up with a patch for it.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-11-01 13:11 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-29 17:53 [Bluez-devel] [PATCH] dbus.c cleanup Johan Hedberg
2005-10-29 18:07 ` Marcel Holtmann
2005-10-29 18:48   ` Johan Hedberg
2005-10-29 19:07     ` Marcel Holtmann
2005-10-31 11:59       ` Claudio Takahasi
2005-10-31 12:07         ` Johan Hedberg
2005-10-31 12:14           ` Marcel Holtmann
2005-10-31 12:30             ` Eduardo Rocha
2005-10-31 12:12         ` Marcel Holtmann
2005-10-31 13:47           ` Claudio Takahasi
2005-11-01 13:11             ` Marcel Holtmann [this message]
2005-11-01 13:21               ` Claudio Takahasi
2005-11-01 19:08                 ` Claudio Takahasi
2005-11-01 19:58                   ` Marcel Holtmann
2005-11-01 20:23                     ` Johan Hedberg
2005-11-01 20:40                       ` Marcel Holtmann
2005-11-01 20:53                       ` Claudio Takahasi
  -- strict thread matches above, loose matches on Subject: below --
2005-11-03  7:20 Johan Hedberg
2005-11-03  8:34 ` Marcel Holtmann
2005-11-03  8:54   ` Johan Hedberg
2005-11-03  9:08     ` Marcel Holtmann
2005-11-03  9:23       ` Johan Hedberg
2005-11-03  9:41         ` Marcel Holtmann
2005-11-03 10:13           ` Johan Hedberg
2005-11-03 10:33             ` Marcel Holtmann
2005-11-03 14:22               ` Johan Hedberg
2005-11-03 14:36                 ` Marcel Holtmann

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=1130850674.31561.65.camel@blade \
    --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