From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org
Cc: Akihiko Odaki <akihiko.odaki@gmail.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PATCH] coreaudio: Notify error in coreaudio_init_out
Date: Sat, 26 Feb 2022 12:30:32 +0100 [thread overview]
Message-ID: <18704456.9KXHJpUyHl@silver> (raw)
In-Reply-To: <f1198af9-1d43-5155-229d-3663c65aec3d@gmail.com>
On Samstag, 26. Februar 2022 11:18:44 CET Akihiko Odaki wrote:
> On 2022/02/26 19:16, Christian Schoenebeck wrote:
> > On Samstag, 26. Februar 2022 11:02:48 CET Akihiko Odaki wrote:
> >> Signed-off-by: Akihiko Odaki <akihiko.odaki@gmail.com>
> >> ---
> >>
> >> audio/coreaudio.c | 2 ++
> >> 1 file changed, 2 insertions(+)
> >>
> >> diff --git a/audio/coreaudio.c b/audio/coreaudio.c
> >> index d8a21d3e507..d7cfdcc4fc4 100644
> >> --- a/audio/coreaudio.c
> >> +++ b/audio/coreaudio.c
> >> @@ -604,6 +604,8 @@ static int coreaudio_init_out(HWVoiceOut *hw, struct
> >> audsettings *as, coreaudio_playback_logerr(status,
> >>
> >> "Could not remove voice property
> >>
> >> change listener\n"); }
> >> +
> >> + return -1;
> >>
> >> }
> >>
> >> return 0;
> >
> > Is this a pure theoretical fix, or does it actually fix an actually
> > encountered misbehaviour? I don't see any explanation in the commit log. I
> > mean the branch here is about removing a listener only.
> >
> > Best regards,
> > Christian Schoenebeck
>
> I saw branching to this block results in abort as core->hw.samples is
> not set.
Ok, then please add an appropriate description to the commit log of what your
observed. Except of that:
Reviewed-by: Christian Schoenebeck <qemu_oss@crudebyte.com>
Best regards,
Christian Schoenebeck
prev parent reply other threads:[~2022-02-26 11:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 10:02 [PATCH] coreaudio: Notify error in coreaudio_init_out Akihiko Odaki
2022-02-26 10:16 ` Christian Schoenebeck
2022-02-26 10:18 ` Akihiko Odaki
2022-02-26 11:30 ` Christian Schoenebeck [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=18704456.9KXHJpUyHl@silver \
--to=qemu_oss@crudebyte.com \
--cc=akihiko.odaki@gmail.com \
--cc=kraxel@redhat.com \
--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.