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 0/7] sound: fix sparse warnings
Date: Wed, 25 Feb 2009 22:26:34 +0100 [thread overview]
Message-ID: <20090225212551.9226.64699.stgit@vmbox.hanneseder.net> (raw)
The following series fixes some sparse warnings in sound/.
---
Hannes Eder (7):
sound/oss: fix sparse warning: symbol shadows an earlier one
sound/oss: fix sparse warnings: different signedness
sound/drivers/vx: fix sparse warning: different signedness
sound/pci/emu10k1: fix sparse warning: different signedness
sound/pci/hda: fix sparse warning: different signedness
sound/usb/usx2y: fix sparse warning: do-while statement is not a compound ...
sound/usb/usx2y: fix sparse warning: Should it be static?
sound/drivers/vx/vx_uer.c | 2 +-
sound/oss/pss.c | 12 ++++++------
sound/oss/sequencer.c | 3 +--
sound/pci/emu10k1/emu10k1_main.c | 10 ++++------
sound/pci/hda/hda_local.h | 2 +-
sound/usb/usx2y/usX2Yhwdep.c | 3 ---
sound/usb/usx2y/usbusx2y.c | 4 ++--
sound/usb/usx2y/usx2yhwdeppcm.h | 2 ++
8 files changed, 17 insertions(+), 21 deletions(-)
next reply other threads:[~2009-02-25 21:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 21:26 Hannes Eder [this message]
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 ` [PATCH 5/7] sound/drivers/vx: " Hannes Eder
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=20090225212551.9226.64699.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®