From: patchwork-bot+bluetooth@kernel.org
To: Igor Skalkin <igor.skalkin@opensynergy.com>
Cc: virtualization@lists.linux-foundation.org, luiz.dentz@gmail.com,
mst@redhat.com, marcel@holtmann.org, johan.hedberg@gmail.com,
jasowang@redhat.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org, Igor.Skalkin@opensynergy.com
Subject: Re: [PATCH v4 1/1] virtio_bt: Fix alignment in configuration struct
Date: Tue, 25 Oct 2022 22:40:16 +0000 [thread overview]
Message-ID: <166673761638.12942.12923887540538153791.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221024134033.30142-2-Igor.Skalkin@opensynergy.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Mon, 24 Oct 2022 15:40:33 +0200 you wrote:
> The current version of the configuration structure has unaligned
> 16-bit fields, but according to the specification [1], access to
> the configuration space must be aligned.
>
> Add a second, aligned version of the configuration structure
> and a new feature bit indicating that this version is being used.
>
> [...]
Here is the summary with links:
- [v4,1/1] virtio_bt: Fix alignment in configuration struct
https://git.kernel.org/bluetooth/bluetooth-next/c/57dc0d471d27
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-10-25 22:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 19:19 [PATCH v3 0/1] virtio_bt: Fix alignment in configuration struct Igor Skalkin
2022-10-18 19:19 ` [PATCH v3 1/1] " Igor Skalkin
2022-10-24 13:40 ` [PATCH v3 0/1] " Igor Skalkin
2022-10-24 13:40 ` [PATCH v4 1/1] " Igor Skalkin
2022-10-24 20:54 ` Luiz Augusto von Dentz
2022-10-25 20:17 ` Igor Skalkin
2022-10-25 20:32 ` Luiz Augusto von Dentz
2022-10-25 22:40 ` patchwork-bot+bluetooth [this message]
2022-10-25 4:04 ` [PATCH v3 0/1] " Michael S. Tsirkin
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=166673761638.12942.12923887540538153791.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=igor.skalkin@opensynergy.com \
--cc=jasowang@redhat.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.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