libata maintainership change

libata maintainership change

[Jeff Garzik]

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

Re: libata maintainership change

[Chris Jones]

On 05/04/2013 06:01 AM, Jeff Garzik wrote:
>
> 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
>
>

All the best in your future projects Jeff. I'm sure your efforts have
been appreciated.


Regards

Chris Jones


-- 
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.4.13 (GNU/Linux)

mQENBFF7bwcBCADREEkM0EcEvY6Zt3Zot5RWk5+a6qMZzj6Qf8tZnG2mjyb/NrOa
ujQhakpkmUj2Cpf04jacEKnjxO5Bk6794QPoSelHAkLFol9XRO6j+94tp+21mrGL
GRHppU8LGGCTrllIJOmKdx2dmqIfYKoRcLs/gA1z0ZrNNz+J3OrcWfDWfVz0eWg6
TeXn4PBAQYr8Ci1fF9/vwxeSQx3PGzJjlzKXsbx/etjICDVVkUAxYkEPbazV1LGx
gwDlhCT5YWQQXdESIbUkQFAbCyglM/HkMNEm23AI/z4PhgjdHBCg8LeQTEUiO+a+
b1ypRMZRpn/je96/PE1ZP5TxaEhaimL+OA+dABEBAAG0JENocmlzIEpvbmVzIDxj
aHJpc2pvbmVzQHNwaW4ubmV0LmF1PokBPgQTAQIAKAUCUXtvBwIbAwUJACdPGQYL
CQgHAwIGFQgCCQoLBBYCAwECHgECF4AACgkQxifpw+rbaJQQBwf+M+arauGqAtkA
LP3Duk0FdDZ3cIbKST3oQd10eACdkH7fQibvtVadkiCeC7CbozSI50o+Snk8/Azd
5V32LkmzUcUEGrnx3B9oZlWMSKZFz5y1rN0YiplQwc4KLq1cSYOZFpVHUZ/ivcJn
k+p+cuLWQrNUI5kiFV+x6lOKIkKgmMrmuKxbwYskPPtE1DIJ7Qh8H/N9aTJ34KAD
+O4dMwDlA2dYDoQYmyCMcly6W6NdPQmww1XX5qmY+obokScIJE5mYUyiFz0kiN6C
NsosjMsUxbrNEPjAfzyU5Y+LqffYJzgyTjlORRqldZU6IDhsmtyDBoshGQFAEm6W
dRQOrNYx6A==
=FJFi
-----END PGP PUBLIC KEY BLOCK-----

Re: libata maintainership change

[Tejun Heo]

Hello,

On Fri, May 03, 2013 at 04:01:33PM -0400, Jeff Garzik wrote:
> 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.

Yes, come high water or fire, I'll soldier on!!!11!!1!one!!

On a more serious note, while I haven't been too active on libata for
quite a while now, I'm fairly confident that I can play the patch
monkey role.  I'll set up a tree and send a pull request to update
MAINTAINERS.

I owe Jeff a lot for holding my hands when I first started hacking on
the kernel.  I don't think I'd be here now if it weren't for his help,
so thanks Jeff and I hope you enjoy whatever your next chapter
brings. :)

Thanks!

-- 
tejun

Re: libata maintainership change

[Nicholas A. Bellinger]

On Fri, 2013-05-03 at 16:01 -0400, Jeff Garzik wrote:
> 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,
> 

Thank you Jeff, and best of luck in all your new endeavors !!

--nab

Re: libata maintainership change

[James Bottomley]

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