From: patchwork-bot+bluetooth@kernel.org
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: marcel@holtmann.org, yake.yang@mediatek.com,
johan.hedberg@gmail.com, luiz.dentz@gmail.com,
matthias.bgg@gmail.com, sean.wang@mediatek.com,
markyawenchen@gmail.com, linux-bluetooth@vger.kernel.org,
linux-mediatek@lists.infradead.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: mt7921s: fix a NULL check
Date: Wed, 23 Mar 2022 10:50:11 +0000 [thread overview]
Message-ID: <164803261159.27387.13243818190116041496.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220323074830.GA4639@kili>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Marcel Holtmann <marcel@holtmann.org>:
On Wed, 23 Mar 2022 10:48:30 +0300 you wrote:
> There is a typo in the NULL check so it's never true. It should be
> checking "*ven_data" instead of "ven_data".
>
> Fixes: 3cabc5ca2c9d ("Bluetooth: mt7921s: Add .btmtk_get_codec_config_data")
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> ---
> drivers/bluetooth/btmtksdio.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Here is the summary with links:
- Bluetooth: mt7921s: fix a NULL check
https://git.kernel.org/bluetooth/bluetooth-next/c/864cc8a234cd
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:[~2022-03-23 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 7:48 [PATCH] Bluetooth: mt7921s: fix a NULL check Dan Carpenter
2022-03-23 7:57 ` 回复: " Yake Yang (杨亚克)
2022-03-23 8:49 ` bluez.test.bot
2022-03-23 8:49 ` bluez.test.bot
2022-03-23 9:18 ` Dan Carpenter
2022-03-23 10:50 ` 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=164803261159.27387.13243818190116041496.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=johan.hedberg@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=markyawenchen@gmail.com \
--cc=matthias.bgg@gmail.com \
--cc=sean.wang@mediatek.com \
--cc=yake.yang@mediatek.com \
/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