From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: Vojtech Pavlik <vojtech@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: PC speaker dead in 2.5.40?
Date: Mon, 07 Oct 2002 16:58:50 -0400 [thread overview]
Message-ID: <3DA1F58A.7030903@nortelnetworks.com> (raw)
In-Reply-To: Pine.NEB.4.44.0210072225320.8340-100000@mimas.fachschaften.tu-muenchen.de
Adrian Bunk wrote:
> Is it
> perhaps possible to move the speaker support to "Character devices"?
Or how about putting it under "Sound"? Seems logical to me.
Chris
next prev parent reply other threads:[~2002-10-07 20:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 16:58 PC speaker dead in 2.5.40? Steve Dover
2002-10-07 7:08 ` Joseph Fannin
2002-10-07 19:14 ` Vojtech Pavlik
2002-10-07 9:46 ` Joseph Fannin
2002-10-07 10:27 ` PC speaker dead in 2.5.40? (resend) Joseph Fannin
2002-10-07 20:32 ` PC speaker dead in 2.5.40? Adrian Bunk
2002-10-07 20:58 ` Chris Friesen [this message]
2002-10-07 16:45 ` Rob Landley
-- strict thread matches above, loose matches on Subject: below --
2002-10-07 19:50 Hell.Surfers
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=3DA1F58A.7030903@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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