From: patchwork-bot+ofono@kernel.org
To: Denis Kenzior <denkenz@gmail.com>
Cc: ofono@lists.linux.dev
Subject: Re: [PATCH 1/2] qmimodem: Rework GET_CARD_STATUS retry logic
Date: Tue, 19 Mar 2024 22:30:29 +0000 [thread overview]
Message-ID: <171088742930.29754.2808290138592394466.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240319164309.2676887-1-denkenz@gmail.com>
Hello:
This series was applied to ofono.git (master)
by Denis Kenzior <denkenz@gmail.com>:
On Tue, 19 Mar 2024 11:42:53 -0500 you wrote:
> Port the retry logic from glib based implementation that uses
> g_timeout_add to use l_timeout instead. While here, fix the existing
> logic to not leak memory when a retry is performed. This happens in one
> of two ways:
>
> - When retry_cbd is allocated via cb_data_new, it is never freed when
> the timeout GSource fires.
> - If the timeout GSource is removed early (i.e. due to remove() being
> called), the associated retry_cbd is not freed
>
> [...]
Here is the summary with links:
- [1/2] qmimodem: Rework GET_CARD_STATUS retry logic
https://git.kernel.org/pub/scm/network/ofono/ofono.git/?id=559c224c4cd3
- [2/2] qmimodem: sms: Silence valgrind warning
https://git.kernel.org/pub/scm/network/ofono/ofono.git/?id=b0f808ccd6e1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-03-19 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 16:42 [PATCH 1/2] qmimodem: Rework GET_CARD_STATUS retry logic Denis Kenzior
2024-03-19 16:42 ` [PATCH 2/2] qmimodem: sms: Silence valgrind warning Denis Kenzior
2024-03-19 22:30 ` patchwork-bot+ofono [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=171088742930.29754.2808290138592394466.git-patchwork-notify@kernel.org \
--to=patchwork-bot+ofono@kernel.org \
--cc=denkenz@gmail.com \
--cc=ofono@lists.linux.dev \
/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.