From: tsbogend@alpha.franken.de (Thomas Bogendoerfer)
To: Martin Michlmayr <tbm@cyrius.com>
Cc: linux-mips@linux-mips.org
Subject: Re: "indy_volume_button" [sound/oss/hal2.ko] undefined
Date: Wed, 13 Aug 2008 22:58:36 +0200 [thread overview]
Message-ID: <20080813205836.GA10796@alpha.franken.de> (raw)
In-Reply-To: <20080813125954.GA3203@deprecation.cyrius.com>
On Wed, Aug 13, 2008 at 03:59:55PM +0300, Martin Michlmayr wrote:
> sound/oss/hal2.ko fails to build because indy_volume_button was
> removed from the IP22 code. Is sound/oss/hal2o going to be removed
> before 2.6.27 is out?
The OSS hal driver is still marked experimental and the only IP22 sound
driver I'll care (and take care) is the alsa one. So if nobody objects
I'll send a remove patch.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2008-08-13 20:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 12:59 "indy_volume_button" [sound/oss/hal2.ko] undefined Martin Michlmayr
2008-08-13 20:58 ` Thomas Bogendoerfer [this message]
2008-08-14 5:41 ` Martin Michlmayr
2008-08-14 6:37 ` Thomas Bogendoerfer
2008-08-14 7:01 ` Martin Michlmayr
2008-08-14 6:30 ` Markus Gothe
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=20080813205836.GA10796@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-mips@linux-mips.org \
--cc=tbm@cyrius.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