[Qemu-devel] [PATCH] qemu-tech: Spelling fixes

[Qemu-devel] [PATCH] qemu-tech: Spelling fixes

[Stefan Weil]

Signed-off-by: Stefan Weil <weil@mail.berlios.de>
---
 qemu-tech.texi |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/qemu-tech.texi b/qemu-tech.texi
index 2e2a081..138e3ce 100644
--- a/qemu-tech.texi
+++ b/qemu-tech.texi
@@ -516,7 +516,7 @@ timers, especially together with the use of bottom halves (BHs).
 @section Hardware interrupts
 
 In order to be faster, QEMU does not check at every basic block if an
-hardware interrupt is pending. Instead, the user must asynchrously
+hardware interrupt is pending. Instead, the user must asynchronously
 call a specific function to tell that an interrupt is pending. This
 function resets the chaining of the currently executing basic
 block. It ensures that the execution will return soon in the main loop
@@ -548,7 +548,7 @@ Linux kernel does. The @code{sigreturn()} system call is emulated to return
 from the virtual signal handler.
 
 Some signals (such as SIGALRM) directly come from the host. Other
-signals are synthetized from the virtual CPU exceptions such as SIGFPE
+signals are synthesized from the virtual CPU exceptions such as SIGFPE
 when a division by zero is done (see @code{main.c:cpu_loop()}).
 
 The blocked signal mask is still handled by the host Linux kernel so
-- 
1.7.2.3

Re: [Qemu-devel] [PATCH] qemu-tech: Spelling fixes

[Blue Swirl]

Thanks, applied.

On Fri, Jan 7, 2011 at 8:31 PM, Stefan Weil <weil@mail.berlios.de> wrote:
> Signed-off-by: Stefan Weil <weil@mail.berlios.de>
> ---
>  qemu-tech.texi |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/qemu-tech.texi b/qemu-tech.texi
> index 2e2a081..138e3ce 100644
> --- a/qemu-tech.texi
> +++ b/qemu-tech.texi
> @@ -516,7 +516,7 @@ timers, especially together with the use of bottom halves (BHs).
>  @section Hardware interrupts
>
>  In order to be faster, QEMU does not check at every basic block if an
> -hardware interrupt is pending. Instead, the user must asynchrously
> +hardware interrupt is pending. Instead, the user must asynchronously
>  call a specific function to tell that an interrupt is pending. This
>  function resets the chaining of the currently executing basic
>  block. It ensures that the execution will return soon in the main loop
> @@ -548,7 +548,7 @@ Linux kernel does. The @code{sigreturn()} system call is emulated to return
>  from the virtual signal handler.
>
>  Some signals (such as SIGALRM) directly come from the host. Other
> -signals are synthetized from the virtual CPU exceptions such as SIGFPE
> +signals are synthesized from the virtual CPU exceptions such as SIGFPE
>  when a division by zero is done (see @code{main.c:cpu_loop()}).
>
>  The blocked signal mask is still handled by the host Linux kernel so
> --
> 1.7.2.3
>
>
>