Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <dje@google.com>
To: Joel Sherrill <joel.sherrill@oarcorp.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Fix spelling error in psim
Date: Thu, 21 Aug 2014 00:10:00 -0000	[thread overview]
Message-ID: <CADPb22RPXv2eZ_D3pU69UxyrqitqNqkrGgRXbS=rqG6FsYxqYQ@mail.gmail.com> (raw)
In-Reply-To: <53F5250D.4030301@oarcorp.com>

On Wed, Aug 20, 2014 at 3:45 PM, Joel Sherrill
<joel.sherrill@oarcorp.com> wrote:
>
> Hi
>
> OK to commit as obvious?
>
> 2014-08-21  Joel Sherrill <joel.sherrill@oarcorp.com>
>
>     * ppc-instructions: Fix spelling error.
>
> diff --git a/sim/ppc/ppc-instructions b/sim/ppc/ppc-instructions
> index 1b8fd89..1a2e51a 100644
> --- a/sim/ppc/ppc-instructions
> +++ b/sim/ppc/ppc-instructions
> @@ -3355,7 +3355,7 @@ void::function::invalid_zero_divide_operation:cpu
> *proces
>           spreg new_val = (spr_length(n) == 64
>                            ? *rS
>                            : MASKED(*rS, 32, 63));
> -         /* HACK - time base registers need to be updated immediatly */
> +         /* HACK - time base registers need to be updated immediately */
>           if (WITH_TIME_BASE) {
>             switch (n) {
>             case spr_tbu:

Yep.
[If this were gdb one might want a "." followed by two spaces here,
but this isn't gdb.  Lucky you. :-)]


  reply	other threads:[~2014-08-21  0:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-20 22:45 Joel Sherrill
2014-08-21  0:10 ` Doug Evans [this message]
2014-08-21  1:14   ` Mike Frysinger
2014-08-21  7:15     ` Joel Brobecker
2014-08-21  8:12       ` Mike Frysinger
2014-08-21 13:46       ` Joel Sherrill
2014-08-27  6:08         ` Joel Brobecker
2014-08-21  1:13 ` Mike Frysinger

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='CADPb22RPXv2eZ_D3pU69UxyrqitqNqkrGgRXbS=rqG6FsYxqYQ@mail.gmail.com' \
    --to=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=joel.sherrill@oarcorp.com \
    /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