Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Cathal Mullaney" <cathal.mullaney2@mail.dcu.ie>
To: alsa-devel@lists.sourceforge.net
Subject: Help Wanted?
Date: Wed, 1 Feb 2006 22:33:43 +0000	[thread overview]
Message-ID: <4345459A000A66C3@hawk.dcu.ie> (raw)

Hullo All,
   I am a recent CS graduate and have been developing C++ applications using
alsa for a number of years now and would like, if possible, to give something
back as it were. As I have been developing apps. with alsa over a variety
of hardware architectures I have noticed a few bugs and unattractive features
which I would be willing to attempt to address. This list seems a sortof
I have a problem with "X" please help me, are there active projects within
ALSA that require developers or should I identify a problem and focus my
attention on it? I have no experience writing device drivers for Linux but
I have read various faqs concerning kernel module programming etc and am
willing to learn any necessary skills. I have a reasonable amount of free
time to devote to such a worthy cause and am always willing to learn new
skills. All I would ask in return is to be credited for anything I contribute.
Anyone willing to put me to work please reply to my email address or to the
list.

Yours Sincerely,
Cathal




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642

             reply	other threads:[~2006-02-01 22:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-01 22:33 Cathal Mullaney [this message]
2006-02-01 22:57 ` Help Wanted? Lee Revell

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=4345459A000A66C3@hawk.dcu.ie \
    --to=cathal.mullaney2@mail.dcu.ie \
    --cc=alsa-devel@lists.sourceforge.net \
    /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