From: Hannes Eder <hannes@hanneseder.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 5/7] sound/drivers/vx: fix sparse warning: different signedness
Date: Wed, 25 Feb 2009 22:29:15 +0100 [thread overview]
Message-ID: <20090225212907.9226.10636.stgit@vmbox.hanneseder.net> (raw)
In-Reply-To: <20090225212551.9226.64699.stgit@vmbox.hanneseder.net>
Fix this sparse warning:
sound/drivers/vx/vx_uer.c:301:42: warning: incorrect type in argument 2 (different signedness)
Signed-off-by: Hannes Eder <hannes@hanneseder.net>
---
sound/drivers/vx/vx_uer.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/sound/drivers/vx/vx_uer.c b/sound/drivers/vx/vx_uer.c
index 0e1ba9b..b0560fe 100644
--- a/sound/drivers/vx/vx_uer.c
+++ b/sound/drivers/vx/vx_uer.c
@@ -103,7 +103,7 @@ static void vx_write_one_cbit(struct vx_core *chip, int index, int val)
* returns the frequency of UER, or 0 if not sync,
* or a negative error code.
*/
-static int vx_read_uer_status(struct vx_core *chip, int *mode)
+static int vx_read_uer_status(struct vx_core *chip, unsigned int *mode)
{
int val, freq;
next prev parent reply other threads:[~2009-02-25 21:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 21:26 [PATCH 0/7] sound: fix sparse warnings Hannes Eder
2009-02-25 21:26 ` [PATCH 1/7] sound/usb/usx2y: fix sparse warning: Should it be static? Hannes Eder
2009-02-25 21:28 ` [PATCH 2/7] sound/usb/usx2y: fix sparse warning: do-while statement is not a compound Hannes Eder
2009-02-25 21:28 ` [PATCH 3/7] sound/pci/hda: fix sparse warning: different signedness Hannes Eder
2009-02-25 21:28 ` [PATCH 4/7] sound/pci/emu10k1: " Hannes Eder
2009-02-25 21:29 ` Hannes Eder [this message]
2009-02-25 21:29 ` [PATCH 6/7] sound/oss: fix sparse warnings: " Hannes Eder
2009-02-25 21:29 ` [PATCH 7/7] sound/oss: fix sparse warning: symbol shadows an earlier one Hannes Eder
2009-02-26 9:01 ` [PATCH 0/7] sound: fix sparse warnings 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=20090225212907.9226.10636.stgit@vmbox.hanneseder.net \
--to=hannes@hanneseder.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/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
all inboxes | Powered by JetHome®