From: ajlennon@dynamicdevices.co.uk
To: ofono@ofono.org
Subject: Documentation on when to free structures in/after callbacks
Date: Wed, 28 Jul 2021 16:32:24 +0000 [thread overview]
Message-ID: <20210728163224.2797.88718@ml01.vlan13.01.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 516 bytes --]
Hi all,
I'm trying to write a driver for Quectel modems as I need some specific bits and bobs - mainly signal strengths for the serving cell and neighbourhood cells
I can't quite get my head around when I am supposed to provide free() functions to to calls and when to free in callbacks on success or error conditions.
Is there a bit of a document somewhere somebody could direct me to that explains this?
Or maybe I am overthinking and somebody could just explain the logic behind it?
Thanks!
Alex
next reply other threads:[~2021-07-28 16:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 16:32 ajlennon [this message]
2021-07-28 17:31 ` Documentation on when to free structures in/after callbacks Denis Kenzior
2021-07-30 13:21 ` ajlennon
2021-07-30 14:20 ` Denis Kenzior
2021-07-30 14:24 ` ajlennon
2021-07-30 14:30 ` Denis Kenzior
2021-07-30 15:12 ` ajlennon
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=20210728163224.2797.88718@ml01.vlan13.01.org \
--to=ajlennon@dynamicdevices.co.uk \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).