From: Ralf Baechle <ralf@linux-mips.org>
To: Brian Foster <brian.foster@innova-card.com>
Cc: Linux-MIPS <linux-mips@linux-mips.org>
Subject: Re: Syntax error in include/asm-mips/gdb-stub.h
Date: Thu, 29 Jan 2009 18:18:32 +0000 [thread overview]
Message-ID: <20090129181830.GC4135@linux-mips.org> (raw)
In-Reply-To: <200901291430.30275.brian.foster@innova-card.com>
On Thu, Jan 29, 2009 at 02:30:29PM +0100, Brian Foster wrote:
> apologies for not sending a patch — I'm working with a rather
> old tree (2.6.21-ish vintage) and am uncertain how useful one
> would be — but just collided with a trivial syntax error in
> include/asm-mips/gdb-stub.h
>
> long lo;
> #ifdef CONFIG_CPU_HAS_SMARTMIPS
> long acx
> #endif
> long cp0_badvaddr;
>
> there is missing semicolon (‘;’) on the centre line (acx).
> this mistake is seems to exist in at least the following
> (and very probably elsewhere (I'm not a git expert!)):
Or in simpler words, in all -stable branches upto and including 2.6.26.
Ralf
next prev parent reply other threads:[~2009-01-29 18:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 13:30 Syntax error in include/asm-mips/gdb-stub.h Brian Foster
2009-01-29 18:18 ` Ralf Baechle [this message]
2009-01-30 8:27 ` Brian Foster
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=20090129181830.GC4135@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=brian.foster@innova-card.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.