Hi Jeff, On 07/24/2011 03:47 AM, Jeff Garzik wrote: >> > +config ATA_DEBUG >> > + bool "ATA debugging" >> > + help >> > + This is an option for use by developers; most people should >> > + say N here. This enables ATA core and driver debugging. >> > + >> > +config ATA_VDEBUG >> > + bool "ATA verbose debugging" >> > + depends on ATA_DEBUG >> > + help >> > + This is an option for use by developers; most people should >> > + say N here. This enables deeper (more verbose) debugging of >> > + the ATA core and drivers. >> > + > There does not seem to be a large, driving need for this. It is > straightforward to update the header file for the esoteric, voluminous > debugging. > When i was debugging my code earlier, i found this more useful and convenient over editing headers. We may need to do this in several header files, if we don't have common header for two source files. Also, having this as config option would be more helpful for people who don't have much knowhow of "how dev_dbg and dev_vdbg works". > If you are missing critical hardware or software errors, that is an > argument that those error messages should be outside of DEBUG/VDEBUG, > shipped with every kernel. That's not my case. I wanted to print debug info. -- viresh -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
