linux-kernel - Re: libata maintainership change

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1367635271.5981.60.camel@dabdike>
Date:	Fri, 03 May 2013 19:41:11 -0700
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	Jeff Garzik <jgarzik@...ox.com>
Cc:	Linux IDE mailing list <linux-ide@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Tejun Heo <tj@...nel.org>
Subject: Re: libata maintainership change

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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/