From: Mark Lord <kernel@teksavvy.com>
To: IDE/ATA development list <linux-ide@vger.kernel.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: hdparm-9.32 released: recommended upgrade
Date: Fri, 24 Sep 2010 02:30:37 -0400 [thread overview]
Message-ID: <4C9C458D.3080703@teksavvy.com> (raw)
In-Reply-To: <4C9C37B7.7060204@teksavvy.com>
On 10-09-24 01:31 AM, Mark Lord wrote:
> hdparm-9.31 is now released, with some fixes to --security,
> and with the nasty warnings mostly removed.
And quickly followed by hdparm-9.32. Upgrade is RECOMMENDED.
Apparently a number of commands in hdparm have been b0rked since 9.27+,
but nobody bothered to email me about them. Doh!
Fixed.
(but the libata/libahci AHCI result_tf problem is still an issue).
next prev parent reply other threads:[~2010-09-24 6:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 23:41 "blocked for more than 120 secs" --> a valid situation, how to prevent? Mark Lord
2010-09-24 0:05 ` Douglas Gilbert
2010-09-24 2:53 ` Mark Lord
2010-09-24 3:51 ` Mark Lord
2010-09-24 9:12 ` Jens Axboe
2010-09-24 13:51 ` [PATCH] block: Prevent hang_check firing during long I/O Mark Lord
2010-09-24 13:52 ` Jens Axboe
2010-09-24 4:41 ` "blocked for more than 120 secs" --> a valid situation, how to prevent? Douglas Gilbert
2010-09-24 0:51 ` Stan Hoeppner
2010-09-24 1:37 ` Kyle McMartin
2010-09-24 3:48 ` Stan Hoeppner
2010-09-24 5:02 ` Douglas Gilbert
2010-09-24 5:31 ` Mark Lord
2010-09-24 6:22 ` Stan Hoeppner
2010-09-24 6:30 ` Mark Lord [this message]
2010-09-24 1:58 ` Maxim Levitsky
2010-09-24 2:08 ` Kyle McMartin
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=4C9C458D.3080703@teksavvy.com \
--to=kernel@teksavvy.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).