From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH 06/11] Add notify at command callback
Date: Wed, 17 Mar 2010 12:23:28 -0600 [thread overview]
Message-ID: <201003171323.28549.denkenz@gmail.com> (raw)
In-Reply-To: <1268836241-4834-6-git-send-email-zhenhua.zhang@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1200 bytes --]
Hi Zhenhua,
> ---
> gatchat/gatserver.c | 38 ++++++++++++++++++++++++++++++++++++++
> 1 files changed, 38 insertions(+), 0 deletions(-)
>
> diff --git a/gatchat/gatserver.c b/gatchat/gatserver.c
> index bbaef52..6e3347c 100644
> --- a/gatchat/gatserver.c
> +++ b/gatchat/gatserver.c
> @@ -227,10 +227,48 @@ static gboolean is_extended_character(const char c)
> }
> }
>
> static GAtServerResult at_command_notify(GAtServer *server, char *command,
> char *prefix)
> {
> GAtServerResult res = G_AT_SERVER_RESULT_ERROR;
> + struct at_command *node;
> +
> + node = g_hash_table_lookup(server->command_list, prefix);
> + if (node && node->notify) {
> + GAtServerRequestType type;
> + GAtResult result;
> +
> + type = get_command_type(command, prefix);
> + if (type == G_AT_SERVER_REQUEST_TYPE_ERROR)
> + return res;
> +
> + result.lines = g_slist_prepend(NULL, command);
> + result.final_or_pdu = 0;
> +
> + res = node->notify(type, &result, node->user_data);
> + }
Are you freeing the slist anywhere? In general you might want to run valgrind
before submitting patches just to make sure there are no visible leaks.
Regards,
-Denis
next prev parent reply other threads:[~2010-03-17 18:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 14:30 [PATCH 01/11] Rename g_at_server_send_result Zhenhua Zhang
2010-03-17 14:30 ` [PATCH 02/11] Add framework of server parser Zhenhua Zhang
2010-03-17 14:30 ` [PATCH 03/11] Add basic command parsing Zhenhua Zhang
2010-03-17 14:30 ` [PATCH 04/11] Add extended " Zhenhua Zhang
2010-03-17 14:30 ` [PATCH 05/11] Add server at command data structure Zhenhua Zhang
2010-03-17 14:30 ` [PATCH 06/11] Add notify at command callback Zhenhua Zhang
2010-03-17 14:30 ` [PATCH 07/11] Add g_at_server_register and unregister callback Zhenhua Zhang
2010-03-17 14:30 ` [PATCH 08/11] Add G_AT_SERVER_RESULT_EXT_ERROR Zhenhua Zhang
2010-03-17 14:30 ` [PATCH 09/11] Fix do not emit error if extended error has emitted Zhenhua Zhang
2010-03-17 14:30 ` [PATCH 10/11] Refactor g_at_server_send_final Zhenhua Zhang
2010-03-17 14:30 ` [PATCH 11/11] Add utilities to send server response Zhenhua Zhang
2010-03-17 18:23 ` Denis Kenzior [this message]
2010-03-17 18:02 ` [PATCH 03/11] Add basic command parsing Denis Kenzior
2010-03-17 17:55 ` [PATCH 02/11] Add framework of server parser Denis Kenzior
2010-03-17 14:38 ` [PATCH 01/11] Rename g_at_server_send_result Zhenhua Zhang
2010-03-17 18:24 ` Denis Kenzior
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=201003171323.28549.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox