From: Zhang Han <zhanghan64@huawei.com>
To: <kraxel@redhat.com>
Cc: hunongda@huawei.com, zhang.zhanghailiang@huawei.com,
qemu-trivial@nongnu.org, qemu-devel@nongnu.org,
alex.chen@huawei.com, zhanghan64@huawei.com
Subject: [PATCH v2 5/7] audio: Don't use '%#' in format strings
Date: Fri, 15 Jan 2021 09:24:29 +0800 [thread overview]
Message-ID: <20210115012431.79533-6-zhanghan64@huawei.com> (raw)
In-Reply-To: <20210115012431.79533-1-zhanghan64@huawei.com>
Use '0x' prefix instead of '%#'
Signed-off-by: Zhang Han <zhanghan64@huawei.com>
---
audio/dsoundaudio.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/audio/dsoundaudio.c b/audio/dsoundaudio.c
index 1891a38bee..f7a3351306 100644
--- a/audio/dsoundaudio.c
+++ b/audio/dsoundaudio.c
@@ -215,7 +215,7 @@ static void dsound_log_hresult (HRESULT hr)
break;
#endif
default:
- AUD_log (AUDIO_CAP, "Reason: Unknown (HRESULT %#lx)\n", hr);
+ AUD_log (AUDIO_CAP, "Reason: Unknown (HRESULT 0x%lx)\n", hr);
return;
}
--
2.29.1.59.gf9b6481aed
next prev parent reply other threads:[~2021-01-15 1:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 1:24 [PATCH v2 0/7]Fix some style problems in audio Zhang Han
2021-01-15 1:24 ` [PATCH v2 1/7] audio: Add braces for statements/fix braces' position Zhang Han
2021-01-15 1:24 ` [PATCH v2 2/7] audio: Add spaces around operator/delete redundant spaces Zhang Han
2021-01-15 9:21 ` Philippe Mathieu-Daudé
2021-01-15 1:24 ` [PATCH v2 3/7] audio: foo* bar" should be "foo *bar" Zhang Han
2021-01-15 1:24 ` [PATCH v2 4/7] audio: Fix lines over 90 characters Zhang Han
2021-01-15 1:24 ` Zhang Han [this message]
2021-01-15 9:20 ` [PATCH v2 5/7] audio: Don't use '%#' in format strings Philippe Mathieu-Daudé
2021-01-15 1:24 ` [PATCH v2 6/7] audio: Suspect code indent for conditional statements Zhang Han
2021-01-15 1:24 ` [PATCH v2 7/7] audio: space prohibited between function name and parenthesis'(' Zhang Han
2021-01-15 1:54 ` [PATCH v2 0/7]Fix some style problems in audio no-reply
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=20210115012431.79533-6-zhanghan64@huawei.com \
--to=zhanghan64@huawei.com \
--cc=alex.chen@huawei.com \
--cc=hunongda@huawei.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=zhang.zhanghailiang@huawei.com \
/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).