From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 3/4] gatchat: Emit notification when command is sent to modem.
Date: Thu, 29 Apr 2010 22:00:27 -0500 [thread overview]
Message-ID: <201004292200.27678.denkenz@gmail.com> (raw)
In-Reply-To: <1272540766-19069-1-git-send-email-andrew.zaborowski@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
Hi Andrew,
> +/*!
> + * Same as g_at_chat_send but with an ability to return a notification the
> + * moment the command finally leaves the queue and is submitted to lower
> + * layer.
> + *
> + * This is useful for cases where the modem's response time needs to be
> + * measured, assuming that the lower layers processing time is shorter
> + * than the minimum accuracy needed.
> + */
> +guint g_at_chat_send_with_callback(GAtChat *chat, const char *cmd,
> + const char **valid_resp,
> + GAtSubmitNotifyFunc sent,
> + GAtResultFunc func,
> + gpointer user_data,
> + GDestroyNotify notify);
> +
So I'm fine with the implementation but the name needs work. Can we use
g_at_chat_send_with_submit_notify? Or maybe g_at_chat_send_full, similar to
how GLib does it.
Perhaps enabling submit_notification for a given command after it has been
submitted with g_at_chat_send?
e.g. g_at_chat_set_submit_notify(GAtChat *chat, guint command,
GAtSubmitNotifyFunc sent, gpointer user_data, GDestroyNotify notify);
Regards,
-Denis
next prev parent reply other threads:[~2010-04-30 3:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 11:32 [PATCH 3/4] gatchat: Emit notification when command is sent to modem Andrzej Zaborowski
2010-04-30 3:00 ` Denis Kenzior [this message]
2010-04-30 5:48 ` Marcel Holtmann
2010-04-30 13:31 ` Denis Kenzior
2010-04-30 13:41 ` Marcel Holtmann
2010-05-03 18:22 ` andrzej zaborowski
2010-05-04 9:07 ` Marcel Holtmann
2010-05-04 13:11 ` Andrzej Zaborowski
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=201004292200.27678.denkenz@gmail.com \
--to=denkenz@gmail.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.