Christoph Hellwig wrote: On Fri, Jul 25, 2008 at 02:30:43PM +1000, Niv Sardi wrote: looks good, checking it in Donald NACKed this one.. Yep, but I changed my mind on it a while ago, the blocklayer er
Christoph Hellwig wrote: On Fri, Jul 25, 2008 at 02:30:43PM +1000, Niv Sardi wrote: looks good, checking it in Donald NACKed this one.. Yep, but I changed my mind on it a while ago, the blocklayer er
Christoph Hellwig wrote: On Fri, May 23, 2008 at 08:23:23AM +0200, Christoph Hellwig wrote: All the error injection is already enabled through ifdef DEBUG, so kill the never set second cpp symbol to
cpp symbols not exposed by Kconfig will never get tested. If you thing it's really useful for release builds (which don't quite agree with) we should just enable it unconditionally. It's just in a fe
Christoph Hellwig wrote: On Fri, May 23, 2008 at 08:23:23AM +0200, Christoph Hellwig wrote: All the error injection is already enabled through ifdef DEBUG, so kill the never set second cpp symbol to
cpp symbols not exposed by Kconfig will never get tested. If you thing it's really useful for release builds (which don't quite agree with) we should just enable it unconditionally. It's just in a fe
All the error injection is already enabled through ifdef DEBUG, so kill the never set second cpp symbol to activate it without the rest of the debugging infrastructure. Signed-off-by: Christoph Hellw
Donald NACKed this one.. Yep, but I changed my mind on it a while ago, the blocklayer error injection looks like a more useful framework for testing with release builds. Niv and I chatted about it an
Christoph Hellwig wrote: On Fri, May 23, 2008 at 08:23:23AM +0200, Christoph Hellwig wrote: All the error injection is already enabled through ifdef DEBUG, so kill the never set second cpp symbol to
cpp symbols not exposed by Kconfig will never get tested. If you thing it's really useful for release builds (which don't quite agree with) we should just enable it unconditionally. It's just in a fe