linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Tedd Ho-Jeong An <hj.tedd.an@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [BlueZ PATCH] mgmt-tester: Fix null dereference issue reported by scan-build
Date: Thu, 23 Jun 2022 23:30:13 +0000	[thread overview]
Message-ID: <165602701395.3875.3030928518602402235.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220623044520.458626-1-hj.tedd.an@gmail.com>

Hello:

This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Wed, 22 Jun 2022 21:45:20 -0700 you wrote:
> From: Tedd Ho-Jeong An <tedd.an@intel.com>
> 
> This patch fixes the null dereference reported by the scan-build.
> 
> tools/mgmt-tester.c:12025:28: warning: Access to field 'cap_len' results
> in a dereference of a null pointer (loaded from variable 'rp')
> [core.NullDereference]
> 
> [...]

Here is the summary with links:
  - [BlueZ] mgmt-tester: Fix null dereference issue reported by scan-build
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=e3c92f1f786f

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-06-23 23:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23  4:45 [BlueZ PATCH] mgmt-tester: Fix null dereference issue reported by scan-build Tedd Ho-Jeong An
2022-06-23  6:34 ` [BlueZ] " bluez.test.bot
2022-06-23 23: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=165602701395.3875.3030928518602402235.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=hj.tedd.an@gmail.com \
    --cc=linux-bluetooth@vger.kernel.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 NNTP newsgroup(s).