From: Patrick Shirkey <pshirkey@boosthardware.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: ALSA-drivers-writing howto updated
Date: Wed, 11 Dec 2002 03:55:33 +0900 [thread overview]
Message-ID: <3DF638A5.3060004@boosthardware.com> (raw)
In-Reply-To: s5hsmx57nij.wl@alsa2.suse.de
Takashi Iwai wrote:
> Hi,
>
> i've updated my alsa-drivers-writing howto document, including
> corrections, more complete example codes in sub-sections, and more
> detailed explanation in some unclear parts (thanks to Phil Kerr).
>
> regarding to conversion to other formats: Kevin Conder already
> proposed to convert to DocBook, but he'll have no time until the next
> weekend.
>
> the document is found at the same place,
>
> http://www.alsa-project.org/~iwai/alsa-drivers-writing.txt
>
> please give your comments, criticism and/or corrections.
>
I forgot you had done that. I have added a link to the documentation
page now.
One day I will go through and do some prose editing unless someone else
beats me to it.
--
Patrick Shirkey - Boost Hardware Ltd.
For the discerning hardware connoisseur
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================
Being on stage with the band in front of crowds shouting, "Get off! No!
We want normal music!", I think that was more like acting than anything
I've ever done.
Goldie, 8 Nov, 2002
The Scotsman
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-12-10 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 18:11 ALSA-drivers-writing howto updated Takashi Iwai
2002-12-10 18:55 ` Patrick Shirkey [this message]
2002-12-10 22:10 ` John S. Denker
2002-12-11 15:49 ` 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=3DF638A5.3060004@boosthardware.com \
--to=pshirkey@boosthardware.com \
--cc=alsa-devel@lists.sourceforge.net \
--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 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.