From: Jeff Garzik <jgarzik@pobox.com>
To: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Cc: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Subject: Orphaned libata patches
Date: Fri, 15 Oct 2004 04:01:05 -0400 [thread overview]
Message-ID: <416F83C1.4000902@pobox.com> (raw)
Here are two patches which I created, but they are incomplete, and their
parent trees have since disappeared or moved on.
A fair amount of REQUEST SENSE work:
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/patch.request-sense.bz2
The easy half of the libata iomap conversion:
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/patch.iomap.bz2
(the remaining half involves iomap'ing >= 4 independent BARs per
controller... yuck.)
I'll continue to work on the iomap conversion, but it will be a few days
before I get back to it (in case you want to beat me to it, Al).
The request sense patch hasn't been touched in a while.
Jeff
reply other threads:[~2004-10-15 8:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=416F83C1.4000902@pobox.com \
--to=jgarzik@pobox.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=linux-ide@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).