From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Elias Oltmanns <eo@nebensachen.de>
Cc: Grant Grundler <grundler@google.com>,
Jeff Garzik <jeff@garzik.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
Tejun Heo <htejun@gmail.com>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4 v2] Add documentation for hard disk shock protection interface
Date: Wed, 8 Oct 2008 20:56:37 +0200 [thread overview]
Message-ID: <200810082056.37215.bzolnier@gmail.com> (raw)
In-Reply-To: <8763o8znuf.fsf@denkblock.local>
On Saturday 04 October 2008, Elias Oltmanns wrote:
> Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> wrote:
> > On Wednesday 17 September 2008 09:40:06 Elias Oltmanns wrote:
> >> Put some information (and pointers to more) into the kernel's doc tree,
> >
> >> describing briefly the interface to the kernel's disk head unloading
> >> facility. Information about how to set up a complete shock protection
> >> system under GNU/Linux can be found on the web and is referenced
> >> accordingly.
> >>
> >> Signed-off-by: Elias Oltmanns <eo@nebensachen.de>
> >
> > applied
>
> Here is some final polish including various spelling corrections
> pointed out by Grant Grundler and Peter Moulder. Also, I have added some
> information about the timing constraints related to disk head parking.
> The patch looks more impressive than it really is and I think it would
> be alright just to incorporate it into the original patch so as not to
> clutter up the git log.
>
> Signed-off-by: Elias Oltmanns <eo@nebensachen.de>
merged into the original patch
next prev parent reply other threads:[~2008-10-08 19:28 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-17 16:28 Disk shock protection in GNU/Linux Elias Oltmanns
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 [this message]
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=200810082056.37215.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=eo@nebensachen.de \
--cc=grundler@google.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 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.