Re: [PATCH] libata: add human-readable error value decoding

Mark Lord wrote:

Same here, but I would like to see it in there under a CONFIG_DEBUG_LIBATA

kernel build option or something. Kind of like the "FANCY_STATUS_DUMPS" flag

that drivers/ide used to have for this kind of stuff.

The long term goal is to enable verbose output with a module option and/or sysfs knob, rather than a compile-time switch.

That's what ata_msg_xxx is for. We just don't have the knob yet. Patches welcome...

	Jeff



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH] libata: add human-readable error value decoding
    • From: Mark Lord <[email protected]>

• References:
  • [PATCH] libata: add human-readable error value decoding
    • From: Robert Hancock <[email protected]>
  • Re: [PATCH] libata: add human-readable error value decoding
    • From: Tejun Heo <[email protected]>
  • Re: [PATCH] libata: add human-readable error value decoding
    • From: Mark Lord <[email protected]>

• Prev by Date: Re: Andi, you broke my laptop :-)
• Next by Date: Re: [RFC] memory hotremove patch take 2 [04/10] (isolate all free pages)
• Previous by thread: Re: [PATCH] libata: add human-readable error value decoding
• Next by thread: Re: [PATCH] libata: add human-readable error value decoding
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]