From: patchwork-bot+ofono@kernel.org
To: Max Rudik <m.rudik@omp.ru>
Cc: ofono@lists.linux.dev, denkenz@gmail.com
Subject: Re: [PATCH 0/4] Fix issues found with static analyzer
Date: Thu, 18 Jul 2024 21:20:33 +0000 [thread overview]
Message-ID: <172133763381.16613.17134476287823045894.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240716101136.44583-1-m.rudik@omp.ru>
Hello:
This series was applied to ofono.git (master)
by Denis Kenzior <denkenz@gmail.com>:
On Tue, 16 Jul 2024 13:11:32 +0300 you wrote:
> This patch series fixes several minor issues found with SVACE
> static analyzer.
>
> Max Rudik (4):
> stemodem: Fix possible NULL dereference
> cbs: Fix possible NULL dereference
> stk: Fix possible NULL dereference
> call-settings: Fix typo
>
> [...]
Here is the summary with links:
- [1/4] stemodem: Fix possible NULL dereference
https://git.kernel.org/pub/scm/network/ofono/ofono.git/?id=8bd3d6573a85
- [2/4] cbs: Fix possible NULL dereference
https://git.kernel.org/pub/scm/network/ofono/ofono.git/?id=5b528ee0fa69
- [3/4] stk: Fix possible NULL dereference
https://git.kernel.org/pub/scm/network/ofono/ofono.git/?id=a4efa493a6aa
- [4/4] call-settings: Fix typo
https://git.kernel.org/pub/scm/network/ofono/ofono.git/?id=40eb7863661a
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-07-18 21:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 10:11 [PATCH 0/4] Fix issues found with static analyzer Max Rudik
2024-07-16 10:11 ` [PATCH 1/4] stemodem: Fix possible NULL dereference Max Rudik
2024-07-16 10:11 ` [PATCH 2/4] cbs: " Max Rudik
2024-07-16 10:11 ` [PATCH 3/4] stk: " Max Rudik
2024-07-16 10:11 ` [PATCH 4/4] call-settings: Fix typo Max Rudik
2024-07-18 21:20 ` 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=172133763381.16613.17134476287823045894.git-patchwork-notify@kernel.org \
--to=patchwork-bot+ofono@kernel.org \
--cc=denkenz@gmail.com \
--cc=m.rudik@omp.ru \
--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