From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: Alan Stern <stern@rowland.harvard.edu>, Greg KH <greg@kroah.com>,
Oliver Neukum <oliver@neukum.org>
Cc: Bill Gatliff <bgat@billgatliff.com>,
Kernel development list <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
linux-omap@vger.kernel.org,
spi-devel-general@lists.sourceforge.net, netdev@vger.kernel.org
Subject: Re: mourning the loss of David Brownell
Date: Tue, 5 Apr 2011 17:21:44 -0700 [thread overview]
Message-ID: <20110406002144.GC6983@xanatos> (raw)
In-Reply-To: <BANLkTi=0Wj56uO0qAwMfkWNg0+PtKFiMiA@mail.gmail.com> <Pine.LNX.4.44L0.1104051350480.1972-100000@iolanthe.rowland.org>
On Tue, Apr 05, 2011 at 02:10:53PM -0400, Alan Stern wrote:
> On Mon, 4 Apr 2011, Greg KH wrote:
>
> > As I have seen this tangentally mentioned already a few times
> > publically, I figured it warranted it's own announcement now.
> >
> > Linux has lost a great developer with the passing of David Brownell
> > recently and he will be greatly missed.
>
> David made contributions to a large number of areas in the Linux
> kernel. Even a quick look through MAINTAINERS will show that he worked
> on USB controllers (OHCI, EHCI, OMAP and others), USB gadgets, USB
> networking, and SPI. He was influential in the core USB design (the
> HCD "glue" layer and the scatter-gather library) and the development of
> Power Management (system sleep and the USB PM implementation). His
> designs were elegant and his code was always a pleasure to read.
>
> He also was a big help to me personally, assisting in my initial entry
> to USB core development. And he was the first person I met at the
> first Linux conference I attended. I too will miss him.
On Tue, Apr 05, 2011 at 11:17:20AM -0700, Bill Gatliff wrote:
> Guys:
>
>
> David Brownell unknowingly inspired me to get involved in Linux as a
> profession. I saw him as an individual working successfully on Free
> and Open Software, and have made an effort to emulate his success for
> over a decade now.
>
> I deeply regret never taking the time to meet and thank him in person.
A reminder that we all are mortal. Since David I can't thank David
either, I'd like to take a moment to thank Greg, Alan, and Oliver.
David, Greg, Alan, and Oliver were really great at putting up with my
newbie questions when I was first working on usbfs2, and I really
appreciate all the help, support, and feedback they've given me over the
years. Thank you!
Sarah Sharp
next prev parent reply other threads:[~2011-04-06 0:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110405034819.GA7872@kroah.com>
2011-04-05 18:10 ` mourning the loss of David Brownell Alan Stern
2011-04-05 18:17 ` Bill Gatliff
2011-04-05 19:07 ` Felipe Balbi
2011-04-05 19:56 ` Bill Gatliff
2011-04-06 0:21 ` Sarah Sharp [this message]
2011-04-06 3:35 ` Jidong Xiao
2011-04-06 17:11 ` Tony Lindgren
[not found] ` <20110406171144.GG17376-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2011-04-09 20:43 ` Kai Svahn
2011-04-05 19:01 ` Grant Likely
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=20110406002144.GC6983@xanatos \
--to=sarah.a.sharp@linux.intel.com \
--cc=bgat@billgatliff.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=stern@rowland.harvard.edu \
/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).