From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: [PATCH 1/4] nettime: Network time plugin implementation
Date: Tue, 08 Feb 2011 07:46:30 -0800 [thread overview]
Message-ID: <1297179990.1520.457.camel@aeonflux> (raw)
In-Reply-To: <1297167915.8586.7.camel@apaila-ThinkPad-T410>
[-- Attachment #1: Type: text/plain, Size: 1796 bytes --]
Hi Antti,
> > > plugins/nettime.c | 326 +++++++++++++++++++++++++++++++++++++++++++++++++++++
> > > 1 files changed, 326 insertions(+), 0 deletions(-)
> > > create mode 100644 plugins/nettime.c
> >
> > I would prefer if we call this nokia-timed.c or in case this actually
> > becomes default part of MeeGo, them maybe meego-timed.c. I would be also
> > fine with {nokia,meego}-nettime.c.
> >
> > Just calling it nettime.c is too generic. It needs to be clear what this
> > is for.
> >
> > > +#define TIMED_PATH "/com/meego/time"
> > > +#define TIMED_SERVICE "com.meego.time"
> >
> > So the intention is to convert the Nokia timed into a MeeGo specific
> > daemon? I would have expected to see com.nokia.timed here.
>
> My understanding is that this will be Meego specific plugin since timed
> is part of Meego. Hence, the service 'com.meego.timed'.
this is fine with me, but so far the timed.git tree has nothing alike
this mentioned. It currently still uses com.nokia.timed.
> > > +struct nt_data {
> > > + gboolean time_available;
> > > + gboolean time_pending;
> > > + time_t nw_time_utc;
> > > + time_t received;
> > > + int dst;
> > > + int time_zone;
> > > + const char *mcc;
> > > + const char *mnc;
> >
> > Why do you bother with these here. You might better just reference the
> > netreg atom. The memory is only valid if netreg atom is present.
>
> Timed expects to receive the mcc and mnc in the time notification.
> However, if the mcc and mnc don't change we don't resend the
> information. These fields contain the mnc and mcc that oFono sent
> in the previous time notification.
But this const pointer points to memory inside netreg. It will never
change. It always points to the same address.
Regards
Marcel
next prev parent reply other threads:[~2011-02-08 15:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 14:49 [PATCH 0/4 v4] Network Time Plugin Antti Paila
2011-02-01 14:49 ` [PATCH 1/4] nettime: Network time plugin implementation Antti Paila
2011-02-03 15:17 ` Aki Niemi
2011-02-07 18:58 ` Marcel Holtmann
2011-02-08 12:25 ` Antti Paila
2011-02-08 15:46 ` Marcel Holtmann [this message]
2011-02-01 14:49 ` [PATCH 2/4] nettime: Makefile.am modification Antti Paila
2011-02-01 14:49 ` [PATCH 3/4] nettime: Documentation Antti Paila
2011-02-01 14:54 ` Jeevaka.Badrappan
2011-02-01 19:58 ` Aki Niemi
2011-02-07 19:00 ` Marcel Holtmann
2011-02-01 14:49 ` [PATCH 4/4] nettime: Mock Timed for testing Antti Paila
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=1297179990.1520.457.camel@aeonflux \
--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