From: Blue Swirl <blauwirbel@gmail.com>
To: Stuart Brady <sdbrady@ntlworld.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Fix typos in comments in exec.c
Date: Sun, 3 May 2009 22:00:23 +0300 [thread overview]
Message-ID: <f43fc5580905031200g4c5495d9yc4474cf8d564fdaf@mail.gmail.com> (raw)
In-Reply-To: <20090503111506.GA6088@miranda.arrow>
On 5/3/09, Stuart Brady <sdbrady@ntlworld.com> wrote:
> This patch fixes several typos in comments in exec.c:
>
> longet -> longer
> recommanded -> recommended
> ajustments -> adjustments
> inconsistancies -> inconsistencies
> phsical -> physical
> positionned -> positioned
> succesfully -> successfully
> regon_offset -> region_offset
>
> and also:
>
> start_region -> start_addr
>
> Signed-off-by: Stuart Brady <stuart.brady@gmail.com>
Thanks, applied.
prev parent reply other threads:[~2009-05-03 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-03 11:15 [Qemu-devel] [PATCH] Fix typos in comments in exec.c Stuart Brady
2009-05-03 19:00 ` Blue Swirl [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=f43fc5580905031200g4c5495d9yc4474cf8d564fdaf@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=sdbrady@ntlworld.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;
as well as URLs for NNTP newsgroup(s).