[PATCH] fix typo in quick quiz 4.17

[PATCH] fix typo in quick quiz 4.17

[Paolo Bonzini]

Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
---
 toolsoftrade/toolsoftrade.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/toolsoftrade/toolsoftrade.tex b/toolsoftrade/toolsoftrade.tex
index 4e85a9c..ccbe0ad 100644
--- a/toolsoftrade/toolsoftrade.tex
+++ b/toolsoftrade/toolsoftrade.tex
@@ -964,7 +964,7 @@ rights to assume that the value of \co{goflag} would never change.
 \QuickQuizAnswer{
 	It depends.
 	If the per-thread variable was accessed only from its thread,
-	and never from a single handler, then no.
+	and never from a signal handler, then no.
 	Otherwise, it is quite possible that \co{ACCESS_ONCE()} is needed.
 	We will see examples of both situations in
 	Section~\ref{sec:count:Signal-Theft Limit Counter Implementation}.
-- 
2.5.0

Re: [PATCH] fix typo in quick quiz 4.17

[Paul E. McKenney]

On Sun, Sep 27, 2015 at 02:02:02PM +0200, Paolo Bonzini wrote:
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

Good catch, applied.

							Thanx, Paul

> ---
>  toolsoftrade/toolsoftrade.tex | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/toolsoftrade/toolsoftrade.tex b/toolsoftrade/toolsoftrade.tex
> index 4e85a9c..ccbe0ad 100644
> --- a/toolsoftrade/toolsoftrade.tex
> +++ b/toolsoftrade/toolsoftrade.tex
> @@ -964,7 +964,7 @@ rights to assume that the value of \co{goflag} would never change.
>  \QuickQuizAnswer{
>  	It depends.
>  	If the per-thread variable was accessed only from its thread,
> -	and never from a single handler, then no.
> +	and never from a signal handler, then no.
>  	Otherwise, it is quite possible that \co{ACCESS_ONCE()} is needed.
>  	We will see examples of both situations in
>  	Section~\ref{sec:count:Signal-Theft Limit Counter Implementation}.
> -- 
> 2.5.0
> 
> --
> To unsubscribe from this list: send the line "unsubscribe perfbook" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>