From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: RE: [PATCH 1/1] emit settings signal before active signal
Date: Mon, 23 Nov 2009 09:09:03 +0100 [thread overview]
Message-ID: <1258963743.2993.15.camel@violet> (raw)
In-Reply-To: <9F0C1DB20AFA954FA1DA05309350433D8C09E071@pdsmsx503.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1399 bytes --]
Hi Martin,
> > > ---
> > > src/gprs.c | 13 +++++++------
> > > 1 files changed, 7 insertions(+), 6 deletions(-)
> >
> > quick question on why? I did remember that Denis and I talked about on
> > IRC, but I forgot what our conclusion on the order of these two signals
> > was. We should really document this. Do you remember? And please prepare
> > a patch that also puts a comment about this in the API documentation.
> I can find below log
>
> (2:02:38 AM) holtmann: Not sure if we need the Settings empty, but for completion it makes sense.
> (2:03:05 AM) holtmann: We might wanna emit the Settings empty before Activated false, so that ConnMan can clean up the interface before it goes away.
> (2:03:27 AM) denkenz: What's the difference?
> (2:03:54 AM) denkenz: strictly speaking we shouldn't even bother for empty settings
> (2:04:05 AM) denkenz: useless signal anyway
> (2:04:13 AM) holtmann: Yeah. Just easier for some code path in ConnMan.
> (2:04:49 AM) denkenz: holtmann: ok, that's simple enough anyway
>
> I cannot find the conclusion on active TRUE order. But I think it should the same with active FALSE.
> So ConnMan can setup interface before set network connected.
sounds good enough for me. Patch has been applied.
However please submit a patch that updates the documentation with the
details about the signal order.
Regards
Marcel
prev parent reply other threads:[~2009-11-23 8:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-21 10:56 [PATCH 1/1] emit settings signal before active signal Martin Xu
2009-11-21 18:14 ` Marcel Holtmann
2009-11-23 5:06 ` Xu, Martin
2009-11-23 8:09 ` 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=1258963743.2993.15.camel@violet \
--to=marcel@holtmann.org \
--cc=ofono@ofono.org \
/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