From: patchwork-bot+bluetooth@kernel.org
To: Brian Gix <brian.gix@intel.com>
Cc: linux-bluetooth@vger.kernel.org, luiz.von.dentz@gmail.com
Subject: Re: [PATCH BlueZ v2 1/2] core: make bt_uuid_hash() portable across archs
Date: Thu, 30 Jun 2022 20:40:13 +0000 [thread overview]
Message-ID: <165662161376.2141.16470202159580279555.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220629211640.65822-1-brian.gix@intel.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 29 Jun 2022 14:16:39 -0700 you wrote:
> bt_uuid_t is defined as a byte array, so it can cause alignment errors
> on some architectures, when the two 64 bit halves are treated as u64s.
> This patch ensures proper alignment across all architectures.
>
> Fixes:
> src/adapter.c: In function ‘bt_uuid_hash’:
> src/adapter.c:3617:8: error: cast increases required alignment of target type [-Werror=cast-align]
> val = (uint64_t *)&uuid_128.value.u128;
> ^
> cc1: all warnings being treated as errors
>
> [...]
Here is the summary with links:
- [BlueZ,v2,1/2] core: make bt_uuid_hash() portable across archs
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=8fc3368db840
- [BlueZ,v2,2/2] core: Fix signed vs unsigned compare
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=31690310c096
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-06-30 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 21:16 [PATCH BlueZ v2 1/2] core: make bt_uuid_hash() portable across archs Brian Gix
2022-06-29 21:16 ` [PATCH BlueZ v2 2/2] core: Fix signed vs unsigned compare Brian Gix
2022-06-29 22:57 ` [BlueZ,v2,1/2] core: make bt_uuid_hash() portable across archs bluez.test.bot
2022-06-30 20:40 ` 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=165662161376.2141.16470202159580279555.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=brian.gix@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.von.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 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).