From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Mundt Subject: Re: [PATCH 1/4] panic: Allow warnings to set different taint flags Date: Tue, 6 Apr 2010 06:46:27 +0900 Message-ID: <20100405214626.GA25192@linux-sh.org> References: <1270319696.12516.321.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jesse Barnes , David Woodhouse , linux-pci@vger.kernel.org, LKML , linux-parisc@vger.kernel.org, linuxppc-dev@ozlabs.org, linux-s390@vger.kernel.org, linux-sh@vger.kernel.org To: Ben Hutchings Return-path: In-Reply-To: <1270319696.12516.321.camel@localhost> List-ID: List-Id: linux-parisc.vger.kernel.org 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 > --- > 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.