From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: btnxpuart: Fix sparse warnings
Date: Tue, 18 Apr 2023 20:01:11 +0000 [thread overview]
Message-ID: <168184807135.10886.14421946935057816182.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230418000704.1937843-1-luiz.dentz@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 17 Apr 2023 17:07:04 -0700 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> This fixes the following sparse warnings:
>
> drivers/bluetooth/btnxpuart.c:681:23: sparse: sparse:
> restricted __le16 degrades to integer
> drivers/bluetooth/btnxpuart.c:690:82: sparse:
> sparse: incorrect type in argument 2 (different base types)
> @@ expected unsigned short [usertype] req_len
> @@ got restricted __le16 [usertype] len @@
> drivers/bluetooth/btnxpuart.c:690:82: sparse:
> expected unsigned short [usertype] req_len
> drivers/bluetooth/btnxpuart.c:690:82: sparse:
> got restricted __le16 [usertype] len
> drivers/bluetooth/btnxpuart.c:694:84: sparse:
> sparse: incorrect type in argument 2 (different base types)
> @@ expected unsigned short [usertype] req_len
> @@ got restricted __le16 [usertype] len @@
> drivers/bluetooth/btnxpuart.c:694:84: sparse:
> expected unsigned short [usertype] req_len
> drivers/bluetooth/btnxpuart.c:694:84: sparse:
> got restricted __le16 [usertype] len
> drivers/bluetooth/btnxpuart.c:708:23: sparse:
> sparse: incorrect type in assignment (different base types)
> @@ expected unsigned int [usertype] requested_len
> @@ got restricted __le16 [usertype] len @@
> drivers/bluetooth/btnxpuart.c:708:23: sparse:
> expected unsigned int [usertype] requested_len
> drivers/bluetooth/btnxpuart.c:708:23: sparse:
> got restricted __le16 [usertype] len
> drivers/bluetooth/btnxpuart.c:787:78: sparse:
> sparse: incorrect type in argument 2 (different base types)
> @@ expected unsigned short [usertype] chipid
> @@ got restricted __le16 [usertype] chip_id @@
> drivers/bluetooth/btnxpuart.c:787:78: sparse:
> expected unsigned short [usertype] chipid
> drivers/bluetooth/btnxpuart.c:787:78: sparse:
> got restricted __le16 [usertype] chip_id
> drivers/bluetooth/btnxpuart.c:810:74: sparse:
> sparse: incorrect type in argument 2 (different base types)
> @@ expected unsigned short [usertype] req_len
> @@ got restricted __le16 [usertype] len @@
> drivers/bluetooth/btnxpuart.c:810:74: sparse:
> expected unsigned short [usertype] req_len
> drivers/bluetooth/btnxpuart.c:810:74: sparse:
> got restricted __le16 [usertype] len
> drivers/bluetooth/btnxpuart.c:815:76: sparse:
> sparse: incorrect type in argument 2 (different base types)
> @@ expected unsigned short [usertype] req_len
> @@ got restricted __le16 [usertype] len @@
> drivers/bluetooth/btnxpuart.c:815:76: sparse:
> expected unsigned short [usertype] req_len
> drivers/bluetooth/btnxpuart.c:815:76: sparse:
> got restricted __le16 [usertype] len
> drivers/bluetooth/btnxpuart.c:834:16: sparse:
> sparse: restricted __le32 degrades to integer
> drivers/bluetooth/btnxpuart.c:843:55: sparse:
> sparse: restricted __le32 degrades to integer
> drivers/bluetooth/btnxpuart.c:844:36: sparse:
> sparse: incorrect type in argument 3 (different base types)
> @@ expected unsigned long [usertype]
> @@ got restricted __le16 [usertype] len @@
> drivers/bluetooth/btnxpuart.c:844:36: sparse:
> expected unsigned long [usertype]
> drivers/bluetooth/btnxpuart.c:844:36: sparse:
> got restricted __le16 [usertype] len
>
> [...]
Here is the summary with links:
- Bluetooth: btnxpuart: Fix sparse warnings
https://git.kernel.org/bluetooth/bluetooth-next/c/183d1a0466eb
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:[~2023-04-18 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 0:07 [PATCH] Bluetooth: btnxpuart: Fix sparse warnings Luiz Augusto von Dentz
2023-04-18 1:08 ` bluez.test.bot
2023-04-18 20:01 ` 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=168184807135.10886.14421946935057816182.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.