From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Linux IDE mailing list <linux-ide@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Tejun Heo <tj@kernel.org>
Subject: Re: libata maintainership change
Date: Fri, 03 May 2013 19:41:11 -0700 [thread overview]
Message-ID: <1367635271.5981.60.camel@dabdike> (raw)
In-Reply-To: <5184179D.5050407@pobox.com>
On Fri, 2013-05-03 at 16:01 -0400, Jeff Garzik wrote:
> 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.
Hm, I keep getting asked when SCSI will die in various fora. To be
honest, I expect, with the newer protocols and architecture models, that
it may actually outlive me.
> 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,
Thanks for looking after libata thus far. All the best in whatever you
choose next and best wishes to the new maintainer.
James
prev parent reply other threads:[~2013-05-04 2:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 20:01 libata maintainership change Jeff Garzik
2013-05-03 21:09 ` Chris Jones
2013-05-03 21:10 ` Tejun Heo
2013-05-04 0:35 ` Nicholas A. Bellinger
2013-05-04 2:41 ` James Bottomley [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=1367635271.5981.60.camel@dabdike \
--to=james.bottomley@hansenpartnership.com \
--cc=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