On Sat, Apr 03, 2010 at 07:34:56PM +0100, Ben Hutchings wrote: > WARN() is used in some places to report firmware or hardware bugs that > are then worked-around. These bugs do not affect the stability of the > kernel and should not set the flag for TAINT_WARN. To allow for this, > add WARN_TAINT() and WARN_TAINT_ONCE() macros that take a taint number > as argument. > > Architectures that implement warnings using trap instructions instead > of calls to warn_slowpath_*() now implement __WARN_TAINT(taint) > instead of __WARN(). > > Signed-off-by: Ben Hutchings <ben@xxxxxxxxxxxxxxx> > --- > Changes since the previous version: > - Added note to Documentation/oops-tracing.txt > - Changed the commit message to distinguish taint numbers from taint > flags > - Removed 'must' from last sentence of commit message; this patch > converts all mainline architectures > This seems to be missing my Tested-by from the last iteration, since there are no functional changes with this version feel free to add it in again. -- 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
