From: Colin Guthrie <gmane@colin.guthr.ie>
To: alsa-devel@alsa-project.org
Subject: [PATCH: alsa-lib] Fix a string format ambiguity
Date: Sat, 17 Apr 2010 10:49:55 +0100 [thread overview]
Message-ID: <hqc085$ft8$1@dough.gmane.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 395 bytes --]
Hi,
Simply patch to fix a format-string ambiguity.
Meant to give this over before 1.0.23 but forgot.
Col
--
Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/
Day Job:
Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
Mandriva Linux Contributor [http://www.mandriva.com/]
PulseAudio Hacker [http://www.pulseaudio.org/]
Trac Hacker [http://trac.edgewall.org/]
[-- Attachment #2: 0501-Fix-a-string-format-ambiguity.patch --]
[-- Type: text/x-patch, Size: 817 bytes --]
>From a57b4e4d1433d14e6fda9b675ade7e901222381b Mon Sep 17 00:00:00 2001
From: Colin Guthrie <cguthrie@mandriva.org>
Date: Sun, 28 Feb 2010 22:25:26 +0000
Subject: [PATCH 501/501] Fix a string format ambiguity
---
src/alisp/alisp.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/src/alisp/alisp.c b/src/alisp/alisp.c
index f3580f9..7575f55 100644
--- a/src/alisp/alisp.c
+++ b/src/alisp/alisp.c
@@ -1712,7 +1712,7 @@ static struct alisp_object * F_princ(struct alisp_instance *instance, struct ali
delete_tree(instance, p1);
p1 = eval(instance, car(p));
if (alisp_compare_type(p1, ALISP_OBJ_STRING))
- snd_output_printf(instance->out, p1->value.s);
+ snd_output_printf(instance->out, "%s", p1->value.s);
else
princ_object(instance->out, p1);
n = cdr(p);
--
1.7.0
[-- Attachment #3: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next reply other threads:[~2010-04-17 9:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-17 9:49 Colin Guthrie [this message]
2010-05-27 8:17 ` [PATCH: alsa-lib] Fix a string format ambiguity Takashi Iwai
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='hqc085$ft8$1@dough.gmane.org' \
--to=gmane@colin.guthr.ie \
--cc=alsa-devel@alsa-project.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).