All of lore.kernel.org
 help / color / mirror / Atom feed
From: Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com>
To: ofono@ofono.org
Subject: Re: [RFC patches 02/13] sms_send_message: add a short roadmap
Date: Tue, 08 Jun 2010 22:00:51 +0000	[thread overview]
Message-ID: <1276034707.2478.41.camel@localhost.localdomain> (raw)
In-Reply-To: <1275055911.4706.72.camel@aeonflux.t-mobile.de>

[-- Attachment #1: Type: text/plain, Size: 1858 bytes --]

On Fri, 2010-05-28 at 07:11 -0700, Marcel Holtmann wrote: 
> Hi Inaky,
> 
> > From: Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com>
> > 
> > ---
> >  src/sms.c |   13 +++++++++++++
> >  1 files changed, 13 insertions(+), 0 deletions(-)
> > 
> > diff --git a/src/sms.c b/src/sms.c
> > index 3a1cff0..594481e 100644
> > --- a/src/sms.c
> > +++ b/src/sms.c
> > @@ -398,6 +398,19 @@ static struct tx_queue_entry *create_tx_queue_entry(GSList *msg_list)
> >  	return entry;
> >  }
> >  
> > +/*
> > + * Pre-process a SMS text message and deliver it [D-BUS' SendMessage()]
> > + *
> > + * @conn: D-BUS connection
> > + * @msg: message data (telephone number and text)
> > + * @data: SMS object to use for transmision
> > + *
> > + * An alphabet is chosen for the text and it (might be) segmented in
> > + * fragments by sms_text_prepare() into @msg_list. A queue list @entry
> > + * is created by create_tx_queue_entry() and g_queue_push_tail()
> > + * appends that entry to the SMS transmit queue. Then the tx_next()
> > + * function is scheduled to run to process the queue.
> > + */
> >  static DBusMessage *sms_send_message(DBusConnection *conn, DBusMessage *msg,
> >  					void *data)
> >  {
> 
> small comments here. So it is D-Bus. That is the official naming in
> documentation we settled on some time ago. Half of the documentation
> might be still using it wrongly, but we might wanna set a good example
> here.

Ack to that -- I'll do a S&R for all of those.

> I don't know how picky gtk-doc is about not having the : for title and
> the empty line after the title. However this is nicely readable inside
> the source code, so I am fine with it.

Actually I am thinking gtk-doc is probably not the best idea to settle
on...it's quite a pain to generate and quite limited. More on this
later.




  reply	other threads:[~2010-06-08 22:00 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-26 19:49 [RFC patches 00/13] misc cleanups and SMS ID API Inaky Perez-Gonzalez
2010-05-26 19:49 ` [RFC patches 01/13] Update .gitignore to ignore cscope databases and backup files Inaky Perez-Gonzalez
2010-05-28 14:08   ` Marcel Holtmann
2010-05-28 14:17     ` =?unknown-8bit?q?Jo=C3=A3o?= Paulo Rechi Vita
2010-05-28 14:29       ` Marcel Holtmann
2010-06-08 22:13         ` Inaky Perez-Gonzalez
2010-05-26 19:49 ` [RFC patches 02/13] sms_send_message: add a short roadmap Inaky Perez-Gonzalez
2010-05-28 14:11   ` Marcel Holtmann
2010-06-08 22:00     ` Inaky Perez-Gonzalez [this message]
2010-05-28 14:34   ` Denis Kenzior
2010-06-08 22:37     ` Inaky Perez-Gonzalez
2010-05-26 19:49 ` [RFC patches 03/13] documentation: add note about referencing standards Inaky Perez-Gonzalez
2010-05-28 14:13   ` Marcel Holtmann
2010-06-08 22:01     ` Inaky Perez-Gonzalez
2010-05-26 19:49 ` [RFC patches 04/13] sms_assembly_add_fragment_backup: clarify how insertion spot is found Inaky Perez-Gonzalez
2010-05-28 14:27   ` Denis Kenzior
2010-06-08 22:10     ` Inaky Perez-Gonzalez
2010-05-26 19:49 ` [RFC patches 05/13] util.h: Add BUILD_BUG_ON() and friends for compile-time assert checking Inaky Perez-Gonzalez
2010-05-28 14:17   ` Marcel Holtmann
2010-06-08 22:03     ` Inaky Perez-Gonzalez
2010-05-26 19:49 ` [RFC patches 06/13] smutil.h: add missing header file dependencies Inaky Perez-Gonzalez
2010-05-28 14:19   ` Marcel Holtmann
2010-06-08 22:04     ` Inaky Perez-Gonzalez
2010-05-28 14:31   ` Denis Kenzior
2010-06-08 22:30     ` Inaky Perez-Gonzalez
2010-05-26 19:49 ` [RFC patches 07/13] write_file: make transaction-safe Inaky Perez-Gonzalez
2010-05-28 14:43   ` Denis Kenzior
2010-06-08 22:38     ` Inaky Perez-Gonzalez
2010-05-26 19:49 ` [RFC patches 08/13] storage: add __attribute__((format)) to {write, read}_file() for printf-like variable arg verification Inaky Perez-Gonzalez
2010-05-28 14:45   ` Denis Kenzior
2010-06-08 22:43     ` Inaky Perez-Gonzalez
2010-05-26 19:49 ` [RFC patches 09/13] Add function doc headers to ofono_sms_{create, register} Inaky Perez-Gonzalez
2010-05-28 14:47   ` Denis Kenzior
2010-06-08 22:58     ` Inaky Perez-Gonzalez
2010-05-26 19:49 ` [RFC patches 10/13] doc: explain debugging options to -d, add a pointer in -h to manpage Inaky Perez-Gonzalez
2010-05-28 14:21   ` Marcel Holtmann
2010-06-08 22:07     ` Inaky Perez-Gonzalez
2010-06-08 23:13       ` Marcel Holtmann
2010-06-08 23:33         ` Inaky Perez-Gonzalez
2010-05-26 19:49 ` [RFC patches 11/13] automake: fix installation of udev rules in VPATH builds Inaky Perez-Gonzalez
2010-05-28 14:25   ` Marcel Holtmann
2010-05-28 14:50   ` Denis Kenzior
2010-05-26 19:49 ` [RFC patches 12/13] SMS: introduce message ID API Inaky Perez-Gonzalez
2010-05-28 14:27   ` Marcel Holtmann
2010-06-08 22:12     ` Inaky Perez-Gonzalez
2010-06-08 23:14       ` Marcel Holtmann
2010-05-26 19:49 ` [RFC patches 13/13] SMS: implement SHA256-based message IDs [incomplete] Inaky Perez-Gonzalez

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=1276034707.2478.41.camel@localhost.localdomain \
    --to=inaky.perez-gonzalez@intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.