From: Frank Cusack <fcusack@fcusack.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: /proc/beep
Date: Thu, 11 Sep 2003 10:22:01 -0700 [thread overview]
Message-ID: <20030911102201.A7005@google.com> (raw)
In-Reply-To: <16223.64813.248941.885060@notabene.cse.unsw.edu.au>; from neilb@cse.unsw.edu.au on Thu, Sep 11, 2003 at 02:42:21PM +1000
On Thu, Sep 11, 2003 at 02:42:21PM +1000, Neil Brown wrote:
> On Wednesday September 10, fcusack@fcusack.com wrote:
> > If not, could at least kd_mksound be exported by default anyway? This
> > would allow homegrown /proc/beep's to not require any kernel mods.
>
> The equivalent can be done with the "input layer" in 2.6.
cool! thanks
/fc
prev parent reply other threads:[~2003-09-11 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 4:14 /proc/beep Frank Cusack
2003-09-11 4:42 ` /proc/beep Neil Brown
2003-09-11 17:22 ` Frank Cusack [this message]
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=20030911102201.A7005@google.com \
--to=fcusack@fcusack.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.