All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Igor Skalkin <Igor.Skalkin@opensynergy.com>
Cc: virtualization@lists.linux-foundation.org, luiz.dentz@gmail.com,
	marcel@holtmann.org, johan.hedberg@gmail.com,
	jasowang@redhat.com, linux-bluetooth@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/1] virtio_bt: Fix alignment in configuration struct
Date: Tue, 25 Oct 2022 00:04:58 -0400	[thread overview]
Message-ID: <20221025000433-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20221024134033.30142-1-Igor.Skalkin@opensynergy.com>

On Mon, Oct 24, 2022 at 03:40:32PM +0200, Igor Skalkin wrote:
> According to specification [1], "For the device-specific configuration
> space, the driver MUST use 8 bit wide accesses for 8 bit wide fields,
> 16 bit wide and aligned accesses for 16 bit wide fields and 32 bit wide
> and aligned accesses for 32 and 64 bit wide fields.".
> 
> Current version of the configuration structure has non-aligned 16bit
> fields.
> 
> This patch adds a second, aligned  version of the configuration structure
> and a new feature bit indicating that this version is being used.


subject should be v4 but besides that, ok.
Will a spec patch be forthcoming?

> [1] https://docs.oasis-open.org/virtio/virtio/v1.1/virtio-v1.1.pdf
> 
> Changes in v4:
>   v3 was corrupted by our smtp server.
> Changes in v3:
>   v2 had been sent from the wrong address, fixed.
> Changes in v2:
>   The first version of this patch just changed the configuration
>   structure in uapi/linux/virtio_bt.h
>   This can not be done, because it will break the userspace, so the
>   second version offers a less radical approach - it introduces a new
>   feature bit and a new configuration structure that both the device
>   and the driver will use if this bit is negotiated.
> 
> Igor Skalkin (1):
>   virtio_bt: Fix alignment in configuration struct
> 
>  drivers/bluetooth/virtio_bt.c  | 16 +++++++++++++---
>  include/uapi/linux/virtio_bt.h |  8 ++++++++
>  2 files changed, 21 insertions(+), 3 deletions(-)
> 
> -- 
> 2.37.2


WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Igor Skalkin <Igor.Skalkin@opensynergy.com>
Cc: johan.hedberg@gmail.com, linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com,
	marcel@holtmann.org
Subject: Re: [PATCH v3 0/1] virtio_bt: Fix alignment in configuration struct
Date: Tue, 25 Oct 2022 00:04:58 -0400	[thread overview]
Message-ID: <20221025000433-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20221024134033.30142-1-Igor.Skalkin@opensynergy.com>

On Mon, Oct 24, 2022 at 03:40:32PM +0200, Igor Skalkin wrote:
> According to specification [1], "For the device-specific configuration
> space, the driver MUST use 8 bit wide accesses for 8 bit wide fields,
> 16 bit wide and aligned accesses for 16 bit wide fields and 32 bit wide
> and aligned accesses for 32 and 64 bit wide fields.".
> 
> Current version of the configuration structure has non-aligned 16bit
> fields.
> 
> This patch adds a second, aligned  version of the configuration structure
> and a new feature bit indicating that this version is being used.


subject should be v4 but besides that, ok.
Will a spec patch be forthcoming?

> [1] https://docs.oasis-open.org/virtio/virtio/v1.1/virtio-v1.1.pdf
> 
> Changes in v4:
>   v3 was corrupted by our smtp server.
> Changes in v3:
>   v2 had been sent from the wrong address, fixed.
> Changes in v2:
>   The first version of this patch just changed the configuration
>   structure in uapi/linux/virtio_bt.h
>   This can not be done, because it will break the userspace, so the
>   second version offers a less radical approach - it introduces a new
>   feature bit and a new configuration structure that both the device
>   and the driver will use if this bit is negotiated.
> 
> Igor Skalkin (1):
>   virtio_bt: Fix alignment in configuration struct
> 
>  drivers/bluetooth/virtio_bt.c  | 16 +++++++++++++---
>  include/uapi/linux/virtio_bt.h |  8 ++++++++
>  2 files changed, 21 insertions(+), 3 deletions(-)
> 
> -- 
> 2.37.2

_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

  parent reply	other threads:[~2022-10-25  4:05 UTC|newest]

Thread overview: 18+ 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 ` Igor Skalkin
2022-10-18 19:19 ` [PATCH v3 1/1] " Igor Skalkin
2022-10-18 19:19   ` Igor Skalkin
2022-10-18 19:54   ` bluez.test.bot
2022-10-18 20:31     ` Luiz Augusto von Dentz
2022-10-24 13:40 ` [PATCH v3 0/1] " Igor Skalkin
2022-10-24 13:40   ` Igor Skalkin
2022-10-24 13:40   ` [PATCH v4 1/1] " Igor Skalkin
2022-10-24 13:40     ` Igor Skalkin
2022-10-24 20:54     ` Luiz Augusto von Dentz
2022-10-25 20:17       ` Igor Skalkin
2022-10-25 20:17         ` Igor Skalkin
2022-10-25 20:32         ` Luiz Augusto von Dentz
2022-10-24 21:15     ` [v4,1/1] " bluez.test.bot
2022-10-25 22:40     ` [PATCH v4 1/1] " patchwork-bot+bluetooth
2022-10-25  4:04   ` Michael S. Tsirkin [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=20221025000433-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --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=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 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.