From: Stefan Weil <weil@mail.berlios.de>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: qemu-trivial@nongnu.org
Subject: [Qemu-devel] [PATCH 08/18] Fix typo in comment (dieing -> dying)
Date: Thu, 28 Apr 2011 17:20:32 +0200 [thread overview]
Message-ID: <1304004042-8334-8-git-send-email-weil@mail.berlios.de> (raw)
In-Reply-To: <1304004042-8334-1-git-send-email-weil@mail.berlios.de>
Signed-off-by: Stefan Weil <weil@mail.berlios.de>
---
linux-user/signal.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/linux-user/signal.c b/linux-user/signal.c
index ce033e9..6fe086b 100644
--- a/linux-user/signal.c
+++ b/linux-user/signal.c
@@ -391,7 +391,7 @@ static void QEMU_NORETURN force_sig(int target_sig)
target_sig, strsignal(host_sig), "core dumped" );
}
- /* The proper exit code for dieing from an uncaught signal is
+ /* The proper exit code for dying from an uncaught signal is
* -<signal>. The kernel doesn't allow exit() or _exit() to pass
* a negative value. To get the proper exit code we need to
* actually die from an uncaught signal. Here the default signal
--
1.7.2.5
next prev parent reply other threads:[~2011-04-28 15:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 15:20 [Qemu-devel] [PATCH 01/18] Fix typos in comments (dependancy -> dependency) Stefan Weil
2011-04-28 15:20 ` [Qemu-devel] [PATCH 02/18] Fix typos in comments (accross -> across) Stefan Weil
2011-04-28 15:20 ` [Qemu-devel] [PATCH 03/18] Fix typos in comments (accessable -> accessible, priveleged -> privileged) Stefan Weil
2011-04-28 15:20 ` [Qemu-devel] [PATCH 04/18] Fix typo in comment (colum -> column) Stefan Weil
2011-04-28 15:20 ` [Qemu-devel] [PATCH 05/18] Fix typo in comment (auxilliary -> auxiliary) Stefan Weil
2011-04-28 15:20 ` [Qemu-devel] [PATCH 06/18] Fix typo in comment (embeded -> embedded) Stefan Weil
2011-04-28 15:20 ` [Qemu-devel] [PATCH 07/18] Fix typo in comment (consistant -> consistent) Stefan Weil
2011-05-04 10:13 ` Alon Levy
2011-04-28 15:20 ` Stefan Weil [this message]
2011-04-28 15:20 ` [Qemu-devel] [PATCH 09/18] Fix typos in comments (imediately -> immediately) Stefan Weil
2011-04-28 15:20 ` [Qemu-devel] [PATCH 10/18] Fix typos in comments (existance -> existence) Stefan Weil
2011-04-28 15:20 ` [Qemu-devel] [PATCH 11/18] Fix typos in comments (interupt -> interrupt) Stefan Weil
2011-04-28 15:20 ` [Qemu-devel] [PATCH 12/18] Fix typos in comments (instanciation -> instantiation) Stefan Weil
2011-04-28 15:20 ` [Qemu-devel] [PATCH 13/18] Fix typos in comments (neccessary -> necessary) Stefan Weil
2011-04-28 15:20 ` [Qemu-devel] [PATCH 14/18] Fix typos in comments and code (occured -> occurred and related) Stefan Weil
2011-04-28 15:20 ` [Qemu-devel] [PATCH 15/18] Fix typo in comment (relevent -> relevant) Stefan Weil
2011-04-28 15:20 ` [Qemu-devel] [PATCH 16/18] Fix typo in comment (responsiblity -> responsibility) Stefan Weil
2011-04-28 15:20 ` [Qemu-devel] [PATCH 17/18] Fix typo in comment (truely -> truly) Stefan Weil
2011-04-28 15:20 ` [Qemu-devel] [PATCH 18/18] Fix typos in comment (threshhold -> threshold, mapp -> map) Stefan Weil
2011-05-03 20:25 ` [Qemu-devel] [PATCH 01/18] Fix typos in comments (dependancy -> dependency) Stefan Weil
2011-05-04 15:18 ` [Qemu-devel] [Qemu-trivial] " Stefan Hajnoczi
2011-05-08 12:00 ` [Qemu-devel] " 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=1304004042-8334-8-git-send-email-weil@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).