On Fri, 2010-03-19 at 01:11 +0000, Ben Hutchings wrote: > We now know how to deal with these tables so that they are harmless. > Don't taint the kernel and don't say the BIOS is 'broken' as this > makes users think of hardware damage. > > Signed-off-by: Ben Hutchings <ben@xxxxxxxxxxxxxxx> > --- > We usually insist that a reported bug is reproducible without a tainted > kernel. In this case, the warning taint is unavoidable and looking for > the warning messages is a waste of time for me as a distribution > maintainer for bug submitters. Nack. The warnings have been extremely useful in tracking these errors and getting BIOS vendors to pay attention. If the taint is a problem, how about making a new BIOS_WARN() which sets a different taint flag. -- David Woodhouse Open Source Technology Centre David.Woodhouse@xxxxxxxxx Intel Corporation -- 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
