From: Jeff Garzik <jgarzik@pobox.com>
To: linux-kernel@vger.kernel.org
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Andrew Morton <akpm@osdl.org>
Subject: Re: Parallel ATA with libata status with the patches I'm working on
Date: Thu, 03 Nov 2005 22:49:55 -0500 [thread overview]
Message-ID: <436ADA63.1090605@pobox.com> (raw)
In-Reply-To: <1131029686.18848.48.camel@localhost.localdomain>
My general take on things:
* Supporting PATA has always been a long term libata goal (and people
have known this for years).
* I try to stay as far as possible away from the fight between Alan and
Bart. As the changelog shows, I've merged libata patches from both.
* Alan's patches do tend to come straight to me, and it would be nice if
he CC'd them to a list (linux-ide).
* Nonetheless, they get exposure in -mm (via libata-dev.git) for a
while, before going upstream.
* The non-core changes, i.e. Alan and Albert's PATA drivers, aren't
going upstream for a while, and will be instead living in -mm (via my
"pata-drivers" libata-dev.git branch) Too much breakage and user
confusion will occur if they are pushed {today|soon}.
* CONFIG_IDE=n is still largely for developers and brave souls only (or
for lucky owners of the newest boxes, which simply don't have PATA on
them at all).
next prev parent reply other threads:[~2005-11-04 3:50 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 14:54 Parallel ATA with libata status with the patches I'm working on Alan Cox
2005-11-03 14:48 ` Russell King
2005-11-03 15:02 ` Bartlomiej Zolnierkiewicz
2005-11-03 15:28 ` David S. Miller
2005-11-03 15:48 ` Bartlomiej Zolnierkiewicz
2005-11-03 16:27 ` Alan Cox
2005-11-03 15:56 ` Alan Cox
2005-11-03 20:55 ` Krzysztof Halasa
2005-11-03 21:29 ` Bartlomiej Zolnierkiewicz
2005-11-03 22:29 ` Krzysztof Halasa
2005-11-03 22:48 ` Bartlomiej Zolnierkiewicz
2005-11-03 22:54 ` Alan Cox
2005-11-04 1:30 ` Rogério Brito
2005-11-04 13:38 ` Alan Cox
2005-11-04 13:41 ` Alan Cox
2005-11-04 23:10 ` Russell King
2005-11-04 23:19 ` Benjamin Herrenschmidt
2005-11-03 15:58 ` Alan Cox
2005-11-03 15:30 ` Russell King
2005-11-03 16:23 ` Alan Cox
2005-11-04 3:35 ` Jeff Garzik
2005-11-04 3:35 ` Jeff Garzik
2005-11-04 8:43 ` Xavier Bestel
2005-11-03 14:58 ` Bartlomiej Zolnierkiewicz
2005-11-03 15:49 ` Alan Cox
2005-11-03 15:34 ` Bartlomiej Zolnierkiewicz
2005-11-04 0:14 ` Mark Lord
2005-11-04 0:17 ` Mark Lord
2005-11-04 1:18 ` Alan Cox
2005-11-04 3:49 ` Jeff Garzik [this message]
2005-11-05 22:31 ` Mark Lord
2005-11-04 6:43 ` Benjamin Herrenschmidt
2005-11-04 7:00 ` Jeff Garzik
2005-11-04 13:34 ` Alan Cox
2005-11-04 21:50 ` Benjamin Herrenschmidt
2005-11-06 20:41 ` Alan Cox
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=436ADA63.1090605@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=linux-kernel@vger.kernel.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