From: Paul Mundt <lethal@linux-sh.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
David Woodhouse <dwmw2@infradead.org>,
linux-pci@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-parisc@vger.kernel.org, linuxppc-dev@ozlabs.org,
linux-s390@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH 1/4] panic: Allow warnings to set different taint flags
Date: Tue, 6 Apr 2010 06:46:27 +0900 [thread overview]
Message-ID: <20100405214626.GA25192@linux-sh.org> (raw)
In-Reply-To: <1270319696.12516.321.camel@localhost>
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@decadent.org.uk>
> ---
> 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.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
David Woodhouse <dwmw2@infradead.org>,
linux-pci@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-parisc@vger.kernel.org, linuxppc-dev@ozlabs.org,
linux-s390@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH 1/4] panic: Allow warnings to set different taint flags
Date: Mon, 05 Apr 2010 21:46:27 +0000 [thread overview]
Message-ID: <20100405214626.GA25192@linux-sh.org> (raw)
In-Reply-To: <1270319696.12516.321.camel@localhost>
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@decadent.org.uk>
> ---
> 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.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: linux-s390@vger.kernel.org, linux-parisc@vger.kernel.org,
linux-sh@vger.kernel.org, linux-pci@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
linuxppc-dev@ozlabs.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH 1/4] panic: Allow warnings to set different taint flags
Date: Tue, 6 Apr 2010 06:46:27 +0900 [thread overview]
Message-ID: <20100405214626.GA25192@linux-sh.org> (raw)
In-Reply-To: <1270319696.12516.321.camel@localhost>
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@decadent.org.uk>
> ---
> 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.
next prev parent reply other threads:[~2010-04-05 21:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-03 18:34 [PATCH 1/4] panic: Allow warnings to set different taint flags Ben Hutchings
2010-04-03 18:34 ` Ben Hutchings
2010-04-03 18:34 ` Ben Hutchings
2010-04-03 18:36 ` [PATCH 2/4] panic: Add taint flag TAINT_FIRMWARE_WORKAROUND ('I') Ben Hutchings
2010-04-05 21:38 ` [PATCH 1/4] panic: Allow warnings to set different taint flags Helge Deller
2010-04-05 21:38 ` Helge Deller
2010-04-05 21:38 ` Helge Deller
2010-04-05 21:46 ` Paul Mundt [this message]
2010-04-05 21:46 ` Paul Mundt
2010-04-05 21:46 ` Paul Mundt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100405214626.GA25192@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=ben@decadent.org.uk \
--cc=dwmw2@infradead.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.