From: "Matthew \"mentor\" Bell" <mentor@madwifi.org>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: ath5k-devel@lists.ath5k.org,
Linux Wireless <linux-wireless@vger.kernel.org>
Subject: Re: [ath5k-devel] Atheros kernel support, joining the company
Date: Thu, 17 Apr 2008 18:07:09 +0100 [thread overview]
Message-ID: <1208452029.2994.0.camel@ibis.bells> (raw)
In-Reply-To: <480561DE.7020205@atheros.com>
On Tue, 2008-04-15 at 19:18 -0700, Luis R. Rodriguez wrote:
> Fellow ath5k hackers,
>
> Good news. I write to you to inform you that I have decided to join
> Atheros as a full time employee, as a Software Engineer, to help them
> with their goals and mission to get every device of Atheros supported
> upstream in the Linux kernel.
Spiffing. Good Luck.
Matthew Bell
prev parent reply other threads:[~2008-04-17 17:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 2:18 Atheros kernel support, joining the company Luis R. Rodriguez
2008-04-16 3:25 ` [ath5k-devel] " Pavel Roskin
2008-04-16 12:46 ` John W. Linville
2008-04-16 16:24 ` [ath5k-devel] " Nick Kossifidis
2008-04-17 17:07 ` Matthew "mentor" Bell [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=1208452029.2994.0.camel@ibis.bells \
--to=mentor@madwifi.org \
--cc=ath5k-devel@lists.ath5k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.com \
/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;
as well as URLs for NNTP newsgroup(s).