All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ronald Tessier <ronald.tessier@linux.intel.com>
To: ofono@ofono.org
Subject: [PATCH 0/2] mmsd: fix problems when unregistering msg
Date: Thu, 22 Mar 2012 17:37:28 +0100	[thread overview]
Message-ID: <1332434252-23551-1-git-send-email-ronald.tessier@linux.intel.com> (raw)

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

Please find changes in mmsd in order to fix problems that occurred when
unregistering messages.

1) the messages table contains mms_message object and not uuid, now
every message is unregister with its correct path when the messages
table is destroyed. Furthermore, don't need to remove the message from
the table using g_hash_table_foreach_remove() since
mms_message_unregister() already removed it from the table.

2) use the msg_path (within the debug statement) before removing the
message from the table which free it

Ronald Tessier (2):
  service: fix object path when unregistering msg
  service: free the msg after tracing its path

 src/service.c |   16 ++++++----------
 1 files changed, 6 insertions(+), 10 deletions(-)

--
1.7.4.1


             reply	other threads:[~2012-03-22 16:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22 16:37 Ronald Tessier [this message]
2012-03-22 16:37 ` [PATCH 1/2] service: fix object path when unregistering msg Ronald Tessier
2012-03-22 16:37 ` [PATCH 2/2] service: free the msg after tracing its path Ronald Tessier
2012-03-22 16:37 ` [PATCH 0/1] mmsd service Ronald Tessier
2012-03-22 16:37 ` [PATCH 1/1] service: remove unused mms_request's members Ronald Tessier
2012-03-22 20:24   ` Marcel Holtmann
2012-03-22 20:23 ` [PATCH 0/2] mmsd: fix problems when unregistering msg Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2012-03-14 10:45 Ronald Tessier

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=1332434252-23551-1-git-send-email-ronald.tessier@linux.intel.com \
    --to=ronald.tessier@linux.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.