From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH_v2] atmodem: Poll SIM state after having entered PIN
Date: Tue, 17 Apr 2012 03:10:33 -0500 [thread overview]
Message-ID: <4F8D2579.6090901@gmail.com> (raw)
In-Reply-To: <4F8D42CA.4050102@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
Hi Guillaume,
>> Who owns the cbd data in this case? Are we not leaking that here?
>>
>
> Yes, we are. I see 2 options here:
> a- Tweaking current at_util_sim_state_query_new(GAtChat *chat,
> guint interval, guint num_times,
> at_util_sim_inserted_cb_t cb,
> void *userdata, GDestroyNotify data_destroy); in
> adding a destroyer for user data
>
> b- Implementing new gpointer at_util_sim_state_query_get_data(struct
> at_util_sim_state_query *req); and free user_data during remove
>
Option a would be fine.
Regards,
-Denis
prev parent reply other threads:[~2012-04-17 8:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 7:52 [PATCH_v2] atmodem: Poll SIM state after having entered PIN Guillaume Zajac
2012-04-17 9:36 ` Marcel Holtmann
2012-04-17 10:15 ` Guillaume Zajac
2012-04-17 8:10 ` Denis Kenzior [this message]
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=4F8D2579.6090901@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