From: "Volker Rümelin" <vr_qemu@t-online.de>
To: Michael Tokarev <mjt@tls.msk.ru>, Gerd Hoffmann <kraxel@redhat.com>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org, qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [PATCH 0/2] hw/audio/hda-codec bug fixes
Date: Mon, 6 Nov 2023 23:19:42 +0100 [thread overview]
Message-ID: <37a09aa4-155f-4d0c-ba0c-c408b7d33abf@t-online.de> (raw)
In-Reply-To: <8d37dc7c-c270-4ce6-8913-e19a71761574@tls.msk.ru>
Am 06.11.23 um 20:54 schrieb Michael Tokarev:
> 05.11.2023 20:23, Volker Rümelin :
>> Patch 1/2 fixes a bug that was reported and correctly diagnosed on the
>> QEMU devel mailing list.
>> https://lists.nongnu.org/archive/html/qemu-devel/2023-08/msg02539.html
>> There was another patch to fix this bug, but I had an objection.
>> https://lists.nongnu.org/archive/html/qemu-devel/2023-08/msg02925.html
>>
>> Patch 2/2 corrects the sense of hda codec property mixer during
>> initialization. It was inverted not too long ago.
>
> It looks like -stable material, is it not?
>
Patch 1/2 ("hw/audio/hda-codec: fix multiplication overflow") is stable
material. Sorry, I forgot to cc qemu-stable.
With best regards,
Volker
prev parent reply other threads:[~2023-11-06 22:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 17:23 [PATCH 0/2] hw/audio/hda-codec bug fixes Volker Rümelin
2023-11-05 17:25 ` [PATCH 1/2] hw/audio/hda-codec: fix multiplication overflow Volker Rümelin
2023-11-06 6:34 ` Marc-André Lureau
2023-11-05 17:25 ` [PATCH 2/2] hw/audio/hda-codec: reenable the audio mixer Volker Rümelin
2023-11-06 6:32 ` Marc-André Lureau
2023-11-06 19:54 ` [PATCH 0/2] hw/audio/hda-codec bug fixes Michael Tokarev
2023-11-06 22:19 ` Volker Rümelin [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=37a09aa4-155f-4d0c-ba0c-c408b7d33abf@t-online.de \
--to=vr_qemu@t-online.de \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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 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).