From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: jeff@garzik.org, linux-ide@vger.kernel.org
Subject: [PATCH 0/4] Small set of further libata patches
Date: Fri, 17 Oct 2008 19:08:20 +0100 [thread overview]
Message-ID: <20081017180655.7781.15021.stgit@localhost.localdomain> (raw)
Sort out ninja32 suspend/resume
Do data draining to fix stuck DRQ errors
First cut at lost IRQ recovery
---
Alan Cox (4):
libata: clean up the SFF code for coding style
libata: Improve timeout handling
libata: Drain data on errors
pata_ninja32: suspend/resume support
drivers/ata/libata-eh.c | 19 +++-
drivers/ata/libata-sff.c | 222 +++++++++++++++++++++++++++++++-------------
drivers/ata/pata_isapnp.c | 12 ++
drivers/ata/pata_ninja32.c | 43 +++++++--
drivers/ata/pata_pcmcia.c | 34 +++++++
include/linux/libata.h | 5 +
6 files changed, 254 insertions(+), 81 deletions(-)
--
"I don't think we should kill you because you are right this time around."
- Cristian Gafton
next reply other threads:[~2008-10-17 18:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 18:08 Alan Cox [this message]
2008-10-17 18:08 ` [PATCH 1/4] pata_ninja32: suspend/resume support Alan Cox
2008-10-28 4:42 ` Jeff Garzik
2008-10-28 9:37 ` Alan Cox
2008-10-17 18:08 ` [PATCH 2/4] libata: Drain data on errors Alan Cox
2008-10-22 15:46 ` Elias Oltmanns
2008-10-22 16:44 ` Alan Cox
2008-10-27 19:14 ` Mark Lord
2008-10-27 21:54 ` Alan Cox
2008-10-17 18:08 ` [PATCH 3/4] libata: Improve timeout handling Alan Cox
2008-10-22 15:47 ` Elias Oltmanns
2008-10-22 16:04 ` Alan Cox
2008-10-17 18:09 ` [PATCH 4/4] libata: clean up the SFF code for coding style Alan Cox
2008-10-22 15:48 ` Elias Oltmanns
2008-10-22 16:02 ` Alan Cox
2008-10-23 0:35 ` Jeff Garzik
2008-10-28 1:49 ` Tejun Heo
2008-10-28 9:47 ` Elias Oltmanns
2008-10-29 2:05 ` Tejun Heo
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=20081017180655.7781.15021.stgit@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--cc=linux-ide@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.