From: Ralf Baechle <ralf@linux-mips.org>
To: David Daney <ddaney@caviumnetworks.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] MIPS: Use WARN() in uasm for better diagnostics.
Date: Tue, 28 Dec 2010 16:31:07 +0100 [thread overview]
Message-ID: <20101228153107.GA375@linux-mips.org> (raw)
In-Reply-To: <1293502709-11454-1-git-send-email-ddaney@caviumnetworks.com>
On Mon, Dec 27, 2010 at 06:18:29PM -0800, David Daney wrote:
> On the off chance that uasm ever warns about overflow, there is no way
> to know what the offending instruction is.
>
> Change the printks to WARNs, so we can get a nice stack trace. It has
> the added benefit of being much more noticeable than the short single
> line warning message, so is less likely to be ignored.
Time to interrupt vacation for some patches :-)
Queued for 2.6.38. Thanks!
Ralf
next prev parent reply other threads:[~2010-12-28 15:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-28 2:18 [PATCH] MIPS: Use WARN() in uasm for better diagnostics David Daney
2010-12-28 15:31 ` Ralf Baechle [this message]
2010-12-28 15:44 ` Sergei Shtylyov
2010-12-28 15:54 ` Ralf Baechle
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=20101228153107.GA375@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=ddaney@caviumnetworks.com \
--cc=linux-mips@linux-mips.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.