From: patchwork-bot+bluetooth@kernel.org
To: Roman Smirnov <r.smirnov@omp.ru>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, s.shtylyov@omp.ru,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org
Subject: Re: [PATCH v2 0/2] Bluetooth: mgmt: remove useless NULL checks
Date: Mon, 04 Mar 2024 21:30:27 +0000 [thread overview]
Message-ID: <170958782724.29902.18161431292915050332.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240301133916.1268403-1-r.smirnov@omp.ru>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 1 Mar 2024 13:39:14 +0000 you wrote:
> Svace reports NULL check after dereference in
> mgmt_set_connectable_complete() and add_ext_adv_params_complete().
> The following patches remove these checks.
>
> The second version has a more compact subjects compared to the
> first version.
>
> [...]
Here is the summary with links:
- [v2,1/2] Bluetooth: mgmt: remove NULL check in mgmt_set_connectable_complete()
https://git.kernel.org/bluetooth/bluetooth-next/c/9f67e5ba6f6c
- [v2,2/2] Bluetooth: mgmt: remove NULL check in add_ext_adv_params_complete()
https://git.kernel.org/bluetooth/bluetooth-next/c/3da5589ad808
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-04 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 13:39 Roman Smirnov
2024-03-01 13:39 ` [PATCH v2 1/2] Bluetooth: mgmt: remove NULL check in mgmt_set_connectable_complete() Roman Smirnov
2024-03-01 13:39 ` [PATCH v2 2/2] Bluetooth: mgmt: remove NULL check in add_ext_adv_params_complete() Roman Smirnov
2024-03-04 21:30 ` patchwork-bot+bluetooth [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=170958782724.29902.18161431292915050332.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=lvc-project@linuxtesting.org \
--cc=marcel@holtmann.org \
--cc=r.smirnov@omp.ru \
--cc=s.shtylyov@omp.ru \
/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
all inboxes | Powered by JetHome®