On Sat, Dec 01, 2012 at 09:36:14AM -0200, Mauro Carvalho Chehab wrote: > Please don't call it as "ras.h". Call it, instead, ras_aer.h > (or something similar) as, if we're moving the tracing back to > include/trace/events/, the same should happen for the memory error > events. As you can see yourself, include/trace/events/ contains one header per topic so having ras_event.h and ras_aer.h or whatever, doesn't fit the scheme. IOW, we want all RAS-specific tracepoints to be collected in a header called ras.h like the rest of the subsystems do it. See rcu.h there for a good example. -- Regards/Gruss, Boris. -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html