From: Elias Oltmanns <eo@nebensachen.de>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Jeff Garzik <jeff@garzik.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Disk shock protection in GNU/Linux
Date: Wed, 17 Sep 2008 18:28:20 +0200 [thread overview]
Message-ID: <87d4j2n3dn.fsf@denkblock.local> (raw)
Hi all,
thanks to a lot of help from Bart and Tejun, who kept reviewing my
patches suggested various improvements / fixes, I am now about to post
the updated patch series. As far as I'm aware, all issues raised have
been addressed and I'm hoping that this series is now fit to be merged.
I gather that Bart is prepared queue the ide part of the series (patch
#3) once the first two patches have been merged. Jeff, assuming that
Tejun will ACK patch #2, can you accept those patches (#1 and #2) and
queue them up for 2.6.28?
Perhaps, Bart can take care of patch #4 along with the one that actually
touches the ide subsystem.
The short summary of the patch series is the same as before (all patches
apply to next-20080916):
1. This is a small patch to ata.h in order to provide a simple check for
support of the unload feature as indicated in a device's ID.
2. Here disk head unloading is implemented in the libata subsystem.
3. The same for ide.
4. A little bit of documentation.
Thank you very much for your cooperation.
Elias
next reply other threads:[~2008-09-17 16:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-17 16:28 Elias Oltmanns [this message]
2008-09-17 16:34 ` [PATCH 1/4 v2] Introduce ata_id_has_unload() Elias Oltmanns
2008-09-17 16:57 ` Tejun Heo
2008-09-18 23:24 ` Bartlomiej Zolnierkiewicz
2008-09-17 16:37 ` [PATCH 2/4 v2] libata: Implement disk shock protection support Elias Oltmanns
2008-09-17 18:03 ` Tejun Heo
2008-09-17 18:08 ` Tejun Heo
2008-09-17 18:09 ` Tejun Heo
2008-09-19 9:49 ` Elias Oltmanns
2008-09-19 12:14 ` Tejun Heo
2008-09-19 14:06 ` Elias Oltmanns
2008-09-19 14:15 ` Tejun Heo
2008-09-19 15:00 ` Elias Oltmanns
2008-09-20 4:48 ` Tejun Heo
2008-09-17 16:38 ` [PATCH 3/4 v2] ide: " Elias Oltmanns
2008-09-18 23:24 ` Bartlomiej Zolnierkiewicz
2008-09-19 0:28 ` Elias Oltmanns
2008-09-19 0:47 ` Bartlomiej Zolnierkiewicz
2008-10-04 9:44 ` Elias Oltmanns
2008-10-04 13:49 ` Elias Oltmanns
2008-10-04 23:16 ` Elias Oltmanns
2008-10-08 18:56 ` Bartlomiej Zolnierkiewicz
2008-09-17 16:40 ` [PATCH 4/4 v2] Add documentation for hard disk shock protection interface Elias Oltmanns
2008-09-18 23:28 ` Bartlomiej Zolnierkiewicz
2008-10-04 9:55 ` Elias Oltmanns
2008-10-08 18:56 ` Bartlomiej Zolnierkiewicz
2008-09-19 4:21 ` Grant Grundler
2008-09-19 12:08 ` Elias Oltmanns
[not found] ` <1221724782.3261.13.camel@raz>
2008-09-19 9:50 ` [PATCH 4/4 v2] Add documentation for hard disk shockprotection interface Elias Oltmanns
2008-09-19 20:03 ` raz ben yehuda
2008-09-19 22:05 ` Elias Oltmanns
2008-09-20 23:25 ` 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=87d4j2n3dn.fsf@denkblock.local \
--to=eo@nebensachen.de \
--cc=bzolnier@gmail.com \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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).