From: "Volker Rümelin" <vr_qemu@t-online.de>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Alexander Bulekov" <alxndr@bu.edu>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
QEMU <qemu-devel@nongnu.org>
Subject: [PATCH 0/1] audio/mixeng: fix clang 10+ warning
Date: Sat, 23 May 2020 22:16:03 +0200 [thread overview]
Message-ID: <6231bee7-8d72-fe5c-9b73-cf27f57ff379@t-online.de> (raw)
This is another attempt to silence the clang 10 warning in
audio/mixeng.c.
The problem was first reported here:
https://lists.nongnu.org/archive/html/qemu-devel/2020-03/msg02270.html
This is Philippe's RFC patch and a discussion:
https://lists.nongnu.org/archive/html/qemu-devel/2020-05/msg00264.html
In that discussion I suggested an explicit type cast, but I changed
my mind.
Volker Rümelin (1):
audio/mixeng: fix clang 10+ warning
audio/mixeng.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
--
2.26.1
next reply other threads:[~2020-05-23 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 20:16 Volker Rümelin [this message]
2020-05-23 20:17 ` [PATCH] audio/mixeng: fix clang 10+ warning Volker Rümelin
2020-05-26 5:51 ` Gerd Hoffmann
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=6231bee7-8d72-fe5c-9b73-cf27f57ff379@t-online.de \
--to=vr_qemu@t-online.de \
--cc=alxndr@bu.edu \
--cc=f4bug@amsat.org \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).