From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: "Gerd Hoffmann" <kraxel@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"BALATON Zoltan" <balaton@eik.bme.hu>,
qemu-devel@nongnu.org
Cc: qemu-devel@nongnu.org, devel@daynix.com,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Akihiko Odaki" <odaki@rsg.ci.i.u-tokyo.ac.jp>,
"Phil Dennis-Jordan" <phil@philjordan.eu>,
"Akihiko Odaki" <odaki@rsg.ci.i.u-tokyo.ac.jp>
Subject: Re: [PATCH v8 6/6] coreaudio: Initialize the buffer for device change
Date: Wed, 04 Mar 2026 12:39:02 +0100 [thread overview]
Message-ID: <1921566.atdPhlSkOF@weasel> (raw)
In-Reply-To: <20260304-coreaudio-v8-6-bf1d40731e73@rsg.ci.i.u-tokyo.ac.jp>
On Wednesday, 4 March 2026 07:16:59 CET Akihiko Odaki wrote:
> Reallocate buffers when the active device change as the required buffer
> size may differ.
>
> Signed-off-by: Akihiko Odaki <odaki@rsg.ci.i.u-tokyo.ac.jp>
> Reviewed-by: Phil Dennis-Jordan <phil@philjordan.eu>
> Acked-by: Christian Schoenebeck <qemu_oss@crudebyte.com>
> ---
> audio/coreaudio.m | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/audio/coreaudio.m b/audio/coreaudio.m
> index 23c3d1f80ac5..e4ec1df971c8 100644
> --- a/audio/coreaudio.m
> +++ b/audio/coreaudio.m
> @@ -471,6 +471,7 @@ static OSStatus init_out_device(CoreaudioVoiceOut *core)
> core->device_id = device_id;
> core->device_frame_size = device_frame_size;
> core->hw.samples = core->buffer_count * core->device_frame_size;
> + audio_generic_initialize_buffer_out(&core->hw);
> core->ioprocid = ioprocid;
>
> return 0;
There is no specific reason to insert that call between the struct
initializers here, or is there? I mean the device is suspended at this point,
so it should not matter. Just looks a bit weird.
But in general, LGTM:
Reviewed-by: Christian Schoenebeck <qemu_oss@crudebyte.com>
next prev parent reply other threads:[~2026-03-04 11:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 6:16 [PATCH v8 0/6] coreaudio fixes Akihiko Odaki
2026-03-04 6:16 ` [PATCH v8 1/6] coreaudio: Remove unnecessary explicit casts Akihiko Odaki
2026-03-04 8:07 ` Marc-André Lureau
2026-03-04 6:16 ` [PATCH v8 2/6] coreaudio: Remove extra whitespaces Akihiko Odaki
2026-03-04 8:06 ` Marc-André Lureau
2026-03-04 6:16 ` [PATCH v8 3/6] coreaudio: Improve naming Akihiko Odaki
2026-03-04 8:07 ` Marc-André Lureau
2026-03-04 9:25 ` Christian Schoenebeck
2026-03-04 10:42 ` Akihiko Odaki
2026-03-04 10:52 ` Christian Schoenebeck
2026-03-04 12:00 ` BALATON Zoltan
2026-03-04 6:16 ` [PATCH v8 4/6] coreaudio: Commit the result of init in the end Akihiko Odaki
2026-03-04 11:56 ` Christian Schoenebeck
2026-03-07 4:10 ` Akihiko Odaki
2026-03-04 6:16 ` [PATCH v8 5/6] audio: Add functions to initialize buffers Akihiko Odaki
2026-03-04 8:11 ` Marc-André Lureau
2026-03-04 8:36 ` Christian Schoenebeck
2026-03-04 10:47 ` Akihiko Odaki
2026-03-04 11:17 ` Christian Schoenebeck
2026-03-07 4:17 ` Akihiko Odaki
2026-03-04 6:16 ` [PATCH v8 6/6] coreaudio: Initialize the buffer for device change Akihiko Odaki
2026-03-04 8:11 ` Marc-André Lureau
2026-03-04 11:39 ` Christian Schoenebeck [this message]
2026-03-07 5:29 ` Akihiko Odaki
2026-03-04 8:42 ` [PATCH v8 0/6] coreaudio fixes Christian Schoenebeck
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=1921566.atdPhlSkOF@weasel \
--to=qemu_oss@crudebyte.com \
--cc=balaton@eik.bme.hu \
--cc=devel@daynix.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=odaki@rsg.ci.i.u-tokyo.ac.jp \
--cc=phil@philjordan.eu \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.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.