From: Ralf Baechle <ralf@linux-mips.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: linux-mips@linux-mips.org
Subject: Re: [MIPS] Work around bogus gcc warnings.
Date: Tue, 6 Feb 2007 11:50:59 +0000 [thread overview]
Message-ID: <20070206115059.GA5660@linux-mips.org> (raw)
In-Reply-To: <20070206.160221.07643905.nemoto@toshiba-tops.co.jp>
On Tue, Feb 06, 2007 at 04:02:21PM +0900, Atsushi Nemoto wrote:
> This commit broke gdb, since any BREAK or TRAP instruction cause
> SIGSEGV.
Applied, thanks.
Ralf
prev parent reply other threads:[~2007-02-06 11:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S20037630AbWK3BWw/20061130012252Z+10493@ftp.linux-mips.org>
2007-02-06 7:02 ` [MIPS] Work around bogus gcc warnings Atsushi Nemoto
2007-02-06 11:50 ` Ralf Baechle [this message]
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=20070206115059.GA5660@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=anemo@mba.ocn.ne.jp \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox