From: Klaus Fuerstberger <kfuerstberger@arcor.de>
To: Kai Makisara <Kai.Makisara@kolumbus.fi>
Cc: Tejun Heo <htejun@gmail.com>,
Bruce Allen <ballen@gravity.phys.uwm.edu>,
Mark Lord <liml@rtr.ca>, David Greaves <david@dgreaves.com>,
Douglas Gilbert <dougg@torque.net>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jeff Garzik <jeff@garzik.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jan Dvorak <fermentol@gmail.com>,
Klaus Fuerstberger <kfuerstberger@arcor.de>,
Bruce Allen <bruce.allen@aei.mpg.de>,
Robert Hancock <hancockr@shaw.ca>
Subject: Re: SMART problems in 2.6.22
Date: Mon, 16 Jul 2007 15:12:17 +0200 [thread overview]
Message-ID: <469B6EB1.1060201@arcor.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0707161453230.5065@kai.makisara.local>
Kai Makisara said the following on 16.07.2007 13:58:
>> Please try the patch in the following message.
>> http://article.gmane.org/gmane.linux.ide/20799/raw
> This solves the 'smartctl -H' problem both of my systems (one with Nvidia
> CK804 and one with MCP51).
This patch also solved the problem I reported here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=428975
Thanks!
Bye Klaus
next prev parent reply other threads:[~2007-07-16 13:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 0:32 SMART problems in 2.6.22 Bruce Allen
2007-07-09 1:14 ` Bruce Allen
2007-07-09 2:09 ` Jeff Garzik
2007-07-09 17:35 ` Bruce Allen
2007-07-09 17:52 ` Jeff Garzik
2007-07-09 18:02 ` Bruce Allen
2007-07-09 23:35 ` [smartmontools-support] " Adam Spiers
2007-07-10 18:22 ` Mark Lord
2007-07-09 11:55 ` David Greaves
2007-07-09 17:56 ` Bruce Allen
2007-07-09 18:00 ` David Greaves
2007-07-09 18:43 ` Jeff Garzik
2007-07-09 21:11 ` Kai Makisara
2007-07-10 4:24 ` Douglas Gilbert
2007-07-11 1:31 ` Bruce Allen
2007-07-16 10:48 ` Kai Makisara
2007-07-16 11:22 ` Tejun Heo
2007-07-16 11:58 ` Kai Makisara
2007-07-16 13:12 ` Klaus Fuerstberger [this message]
2007-07-16 21:27 ` Bruce Allen
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=469B6EB1.1060201@arcor.de \
--to=kfuerstberger@arcor.de \
--cc=Kai.Makisara@kolumbus.fi \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ballen@gravity.phys.uwm.edu \
--cc=bruce.allen@aei.mpg.de \
--cc=david@dgreaves.com \
--cc=dougg@torque.net \
--cc=fermentol@gmail.com \
--cc=hancockr@shaw.ca \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=liml@rtr.ca \
--cc=linux-kernel@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