All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andrew Morton <akpm@osdl.org>, linux-ide@vger.kernel.org
Subject: Re: [PATCH]: libata-core: Add support for ATA_HORKAGE_DIAGNOSTIC
Date: Fri, 09 Mar 2007 08:05:24 -0500	[thread overview]
Message-ID: <45F15B94.7050208@garzik.org> (raw)
In-Reply-To: <20070309140318.174a95b3@lxorguk.ukuu.org.uk>

Alan Cox wrote:
>>> -                if (print_info) {
>>> +                if (print_info && !(ata_device_blacklisted(dev) & ATA_HORKAGE_DIAGNOSTIC)) {
>>>  			ata_dev_printk(dev, KERN_WARNING,
>>>  "Drive reports diagnostics failure. This may indicate a drive\n");
>>>  			ata_dev_printk(dev, KERN_WARNING,
>> I don't understand this one at all.
>>
>> The original point of the message was to poke people so that they poke 
>> their vendors into fixing the firmware, which is indeed non-spec.  I 
>> would rather not silence a "your device is operating out-of-spec" warning.
> 
> The moment it goes near a business oriented distribution this becomes a
> problem because the flack all lands on either the system vendor or the OS
> product vendor both of whom will simply delete the check. At least this
> way it stays in for cases that actually matter.

Maybe, but it's also possible the vendor and user will know that their 
device is operating out-of-spec.

libata will default to the more-information setting, and distros are 
free to change it if they wish.

	Jeff




      reply	other threads:[~2007-03-09 13:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-08 23:18 [PATCH]: libata-core: Add support for ATA_HORKAGE_DIAGNOSTIC Alan Cox
2007-03-09 12:48 ` Jeff Garzik
2007-03-09 14:03   ` Alan Cox
2007-03-09 13:05     ` Jeff Garzik [this message]

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=45F15B94.7050208@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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.