From: patchwork-bot+bluetooth@kernel.org
To: Luca Weiss <luca.weiss@fairphone.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, gubbaven@codeaurora.org,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, johan.hedberg@intel.com,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
simon.horman@corigine.com
Subject: Re: [PATCH] Bluetooth: btqca: make sure to handle byte order for soc_id
Date: Fri, 19 May 2023 20:20:20 +0000 [thread overview]
Message-ID: <168452762053.10748.12822242658004808633.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230510-btqca-byte-order-v1-1-82e6a371c5aa@fairphone.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 10 May 2023 11:27:21 +0200 you wrote:
> The field soc_id in struct qca_btsoc_version is __le32 so we need to
> convert it to host byteorder before using.
>
> Reported-by: Simon Horman <simon.horman@corigine.com>
> Fixes: 059924fdf6c1 ("Bluetooth: btqca: Use NVM files based on SoC ID for WCN3991")
> Signed-off-by: Luca Weiss <luca.weiss@fairphone.com>
>
> [...]
Here is the summary with links:
- Bluetooth: btqca: make sure to handle byte order for soc_id
https://git.kernel.org/bluetooth/bluetooth-next/c/0f1e103dc579
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-05-19 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 9:27 [PATCH] Bluetooth: btqca: make sure to handle byte order for soc_id Luca Weiss
2023-05-10 13:11 ` Simon Horman
2023-05-19 20:20 ` 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=168452762053.10748.12822242658004808633.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=gubbaven@codeaurora.org \
--cc=johan.hedberg@gmail.com \
--cc=johan.hedberg@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.weiss@fairphone.com \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=phone-devel@vger.kernel.org \
--cc=simon.horman@corigine.com \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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