From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] build sound/sound_firmware.c only for OSS
Date: Mon, 04 Sep 2006 13:11:04 +0100 [thread overview]
Message-ID: <1157371864.30801.38.camel@localhost.localdomain> (raw)
In-Reply-To: <20060904114135.GO4416@stusta.de>
Ar Llu, 2006-09-04 am 13:41 +0200, ysgrifennodd Adrian Bunk:
> All sound/sound_firmware.c contains is mod_firmware_load() that is a
> legacy API only used by some OSS drivers.
>
> This patch builds it into an own sound_firmware module that is only
> built depending on CONFIG_SOUND_PRIME making the kernel slightly smaller
> for ALSA users.
Reminds me - might as well fix this too
Signed-off-by: Alan Cox <alan@redhat.com>
--- sound/sound_firmware.c~ 2006-09-04 12:33:08.805282488 +0100
+++ sound/sound_firmware.c 2006-09-04 12:33:08.817280664 +0100
@@ -59,8 +59,7 @@
* value zero on a failure.
*
* Caution: This API is not recommended. Firmware should be loaded via
- * an ioctl call and a setup application. This function may disappear
- * in future.
+ * request_firmware.
*/
int mod_firmware_load(const char *fn, char **fp)
--
VGER BF report: H 2.96182e-15
next prev parent reply other threads:[~2006-09-04 11:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 11:41 [RFC: 2.6 patch] build sound/sound_firmware.c only for OSS Adrian Bunk
2006-09-04 12:11 ` Alan Cox [this message]
2006-09-05 12:26 ` [Alsa-devel] " Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2006-08-22 14:46 Adrian Bunk
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=1157371864.30801.38.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=alsa-devel@alsa-project.org \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.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