From: Lennart Poettering <mznyfn@0pointer.de>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Linux Plumbers Conference CFP
Date: Thu, 19 Jun 2008 17:19:29 +0200 [thread overview]
Message-ID: <20080619151929.GA17165@tango.0pointer.de> (raw)
Heya!
Anyone doing (audio) infrastructure work on Linux? If so, please make
sure to join us at the Linux Plumbers Conference in Portland/Oregon in
September. I will be doing an Audio track there and would like to make
sure that everyone who does audio infrastructure work will submit a
paper, or at least attend, or maybe just know about this conference!
It's a conference about the kernel-userspace interfacing, about the
lower levels in our software stack.
For further details, checkout the conference website:
http://www.linuxplumbersconf.org/
Or this blog story of mine:
http://0pointer.de/blog/projects/plumbersconf.html
Spread the word!
Thanks,
Lennart
(Sorry for this Spam!)
--
Lennart Poettering Red Hat, Inc.
lennart [at] poettering [dot] net ICQ# 11060553
http://0pointer.net/lennart/ GnuPG 0x1A015CC4
next reply other threads:[~2008-06-19 15:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 15:19 Lennart Poettering [this message]
2008-06-19 16:25 ` Linux Plumbers Conference CFP Tobin Davis
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=20080619151929.GA17165@tango.0pointer.de \
--to=mznyfn@0pointer.de \
--cc=alsa-devel@alsa-project.org \
/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