From: patchwork-bot+ofono@kernel.org
To: Denis Kenzior <denkenz@gmail.com>
Cc: ofono@lists.linux.dev
Subject: Re: [PATCH 1/4] voicecall: Drop unused GError variables
Date: Thu, 29 Feb 2024 20:40:33 +0000 [thread overview]
Message-ID: <170923923375.24686.15540341116437626583.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240229180746.1671015-1-denkenz@gmail.com>
Hello:
This series was applied to ofono.git (master)
by Denis Kenzior <denkenz@gmail.com>:
On Thu, 29 Feb 2024 12:07:33 -0600 you wrote:
> GError return variables would possibly be allocated by g_key_file_get_*
> functions, but never used and never freed. Fix that.
> ---
> src/voicecall.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
Here is the summary with links:
- [1/4] voicecall: Drop unused GError variables
https://git.kernel.org/pub/scm/network/ofono/ofono.git/?id=8165dc6c175f
- [2/4] smsutil: ensure the address length in bytes <= 10
https://git.kernel.org/pub/scm/network/ofono/ofono.git/?id=a90421d8e45d
- [3/4] smsutil: Check cbs_dcs_decode return value
https://git.kernel.org/pub/scm/network/ofono/ofono.git/?id=7f2adfa22fba
- [4/4] simutil: Make sure set_length on the parent succeeds
https://git.kernel.org/pub/scm/network/ofono/ofono.git/?id=07f48b23e387
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-02-29 20:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 18:07 [PATCH 1/4] voicecall: Drop unused GError variables Denis Kenzior
2024-02-29 18:07 ` [PATCH 2/4] smsutil: ensure the address length in bytes <= 10 Denis Kenzior
2024-02-29 18:07 ` [PATCH 3/4] smsutil: Check cbs_dcs_decode return value Denis Kenzior
2024-02-29 18:07 ` [PATCH 4/4] simutil: Make sure set_length on the parent succeeds Denis Kenzior
2024-02-29 20:40 ` 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=170923923375.24686.15540341116437626583.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 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).