From: Stefan Weil <weil@mail.berlios.de>
To: QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PATCH] Fix some comments (spelling)
Date: Sun, 19 Apr 2009 14:00:20 +0200 [thread overview]
Message-ID: <49EB1254.1090201@mail.berlios.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1 bytes --]
[-- Attachment #2: spelling.patch --]
[-- Type: text/x-diff, Size: 1652 bytes --]
Fix some comments (spelling).
Signed-off-by: Stefan Weil <weil@mail.berlios.de>
Index: trunk/exec.c
===================================================================
--- trunk.orig/exec.c 2009-04-19 13:32:50.000000000 +0200
+++ trunk/exec.c 2009-04-19 13:33:07.000000000 +0200
@@ -420,7 +420,7 @@
/* in user mode, phys_ram_size is not meaningful */
code_gen_buffer_size = DEFAULT_CODE_GEN_BUFFER_SIZE;
#else
- /* XXX: needs ajustments */
+ /* XXX: needs adjustments */
code_gen_buffer_size = (unsigned long)(ram_size / 4);
#endif
}
@@ -2314,7 +2314,7 @@
page size. If (phys_offset & ~TARGET_PAGE_MASK) != 0, then it is an
io memory page. The address used when calling the IO function is
the offset from the start of the region, plus region_offset. Both
- start_region and regon_offset are rounded down to a page boundary
+ start_region and region_offset are rounded down to a page boundary
before calculating this offset. This should not be a problem unless
the low bits of start_addr and region_offset differ. */
void cpu_register_physical_memory_offset(target_phys_addr_t start_addr,
Index: trunk/vnc.c
===================================================================
--- trunk.orig/vnc.c 2009-04-19 13:32:21.000000000 +0200
+++ trunk/vnc.c 2009-04-19 13:33:07.000000000 +0200
@@ -65,7 +65,7 @@
}
/* Enough for the existing format + the 2 vars we're
- * subsituting in. */
+ * substituting in. */
addrlen = strlen(format) + strlen(host) + strlen(serv);
addr = qemu_malloc(addrlen + 1);
snprintf(addr, addrlen, format, host, serv);
reply other threads:[~2009-04-19 12:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=49EB1254.1090201@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).