From: Jeff Garzik <jgarzik@pobox.com>
To: Linux IDE mailing list <linux-ide@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Tejun Heo <tj@kernel.org>
Subject: libata maintainership change
Date: Fri, 03 May 2013 16:01:33 -0400 [thread overview]
Message-ID: <5184179D.5050407@pobox.com> (raw)
Linux has really found its groove.
When I first got involved in Linux, there was no PCI API (now called the
hotplug or device API), and patch submission was a moderately painful
process of throwing spaghetti at a wall: sending and resending, with
both Linus and maintainers having to manually resolve merge conflicts.
<shiver>
It was a real fight to get any Linux hardware support at all. The vast
amount of hardware documentation was locked away or simply unavailable.
Working on memory management or filesystems or scheduling was always the
Sexy Rock Star PhD work that attracted engineers. OTOH, I felt, device
drivers were ignored as boring, unsexy grunt work. Which, ok, maybe it
was. Each new device driver, though, spread Linux to more and greater
locales. Alan Cox and Don Becker did enormous heavy lifting back then.
Now Linux is where it is today, with most hardware vendors actively
seeking open source driver support (except NVIDIA, natch). The kernel
has come a long way.
Time for new open source pastures outside the kernel, for me. SATA is
slowly getting unexciting to the world. Which, really, just means the
brand new technology has reached a usable plateau. :) And maybe in a
few years, with directly attached PCI-NextGenSuperFastExpress storage,
ATA and SCSI will be distant memories.
Until such time as block-based storage disappears from this earth, the
brave Sir Tejun, basically the libata co-author at this point, has
agreed to be a target for slings and arrows known as libata patches.
All the best,
Jeff
next reply other threads:[~2013-05-03 20:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 20:01 Jeff Garzik [this message]
2013-05-03 21:09 ` libata maintainership change Chris Jones
2013-05-03 21:10 ` Tejun Heo
2013-05-04 0:35 ` Nicholas A. Bellinger
2013-05-04 2:41 ` James Bottomley
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=5184179D.5050407@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.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