qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: "Peter A. G. Crosthwaite" <peter.crosthwaite@petalogix.com>
Cc: qemu-trivial@nongnu.org, peter.maydell@linaro.org,
	qemu-devel@nongnu.org, Stefan Weil <sw@weilnetz.de>
Subject: Re: [Qemu-devel] [PATCH] arm: translate: comment typo - s/middel/middle/
Date: Mon, 06 Aug 2012 16:12:52 +0200	[thread overview]
Message-ID: <501FD0E4.9090000@suse.de> (raw)
In-Reply-To: <1344236756-9660-1-git-send-email-peter.crosthwaite@petalogix.com>

Am 06.08.2012 09:05, schrieb Peter A. G. Crosthwaite:
> Signed-off-by: Peter A. G. Crosthwaite <peter.crosthwaite@petalogix.com>
> ---
>  target-arm/translate.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/target-arm/translate.c b/target-arm/translate.c
> index 29008a4..494c682 100644
> --- a/target-arm/translate.c
> +++ b/target-arm/translate.c
> @@ -9892,7 +9892,7 @@ static inline void gen_intermediate_code_internal(CPUARMState *env,
>      } else {
>          /* While branches must always occur at the end of an IT block,
>             there are a few other things that can cause us to terminate
> -           the TB in the middel of an IT block:
> +           the TB in the middle of an IT block:
>              - Exception generating instructions (bkpt, swi, undefined).
>              - Page boundaries.
>              - Hardware watchpoints.

FWIW

Reviewed-by: Andreas Färber <afaerber@suse.de>

/-F

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2012-08-06 14:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-06  7:05 [Qemu-devel] [PATCH] arm: translate: comment typo - s/middel/middle/ Peter A. G. Crosthwaite
2012-08-06 14:12 ` Andreas Färber [this message]
2012-08-06 14:17 ` Peter Maydell
2012-08-10 13:35 ` [Qemu-devel] [Qemu-trivial] " Stefan Hajnoczi

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=501FD0E4.9090000@suse.de \
    --to=afaerber@suse.de \
    --cc=peter.crosthwaite@petalogix.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=sw@weilnetz.de \
    /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;
as well as URLs for NNTP newsgroup(s).