[PATCH] defer: Correct grammar

[PATCH] defer: Correct grammar

[Yubin Ruan]

From 9d049c1dcc544588c12c989ff433fa88e999e4bb Mon Sep 17 00:00:00 2001
From: Yubin Ruan <ablacktshirt@gmail.com>
Date: Sun, 29 Oct 2017 11:36:21 +0800
Subject: [PATCH] defer: Correct grammar

Signed-off-by: Yubin Ruan <ablacktshirt@gmail.com>
---
 defer/rcufundamental.tex | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/defer/rcufundamental.tex b/defer/rcufundamental.tex
index ef3e4d4..4c16478 100644
--- a/defer/rcufundamental.tex
+++ b/defer/rcufundamental.tex
@@ -157,8 +157,8 @@ cause the values of \co{p->a}, \co{p->b}, and
 \co{p->c} to be fetched before the value of \co{p}.
 This is perhaps easiest to see in the case of value-speculation
 compiler optimizations, where the compiler guesses the value
-of \co{p} fetches \co{p->a}, \co{p->b}, and
-\co{p->c} then fetches the actual value of \co{p}
+of \co{p}, fetches \co{p->a}, \co{p->b}, and
+\co{p->c}, and then fetches the actual value of \co{p}
 in order to check whether its guess was correct.
 This sort of optimization is quite aggressive, perhaps insanely so,
 but does actually occur in the context of profile-driven optimization.
-- 
2.7.4

Re: [PATCH] defer: Correct grammar

[Paul E. McKenney]

On Sun, Oct 29, 2017 at 11:37:50AM +0800, Yubin Ruan wrote:
> >From 9d049c1dcc544588c12c989ff433fa88e999e4bb Mon Sep 17 00:00:00 2001
> From: Yubin Ruan <ablacktshirt@gmail.com>
> Date: Sun, 29 Oct 2017 11:36:21 +0800
> Subject: [PATCH] defer: Correct grammar
> 
> Signed-off-by: Yubin Ruan <ablacktshirt@gmail.com>

Good catch, much clearer!  Applied and pushed, thank you!

							Thanx, Paul

> ---
>  defer/rcufundamental.tex | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/defer/rcufundamental.tex b/defer/rcufundamental.tex
> index ef3e4d4..4c16478 100644
> --- a/defer/rcufundamental.tex
> +++ b/defer/rcufundamental.tex
> @@ -157,8 +157,8 @@ cause the values of \co{p->a}, \co{p->b}, and
>  \co{p->c} to be fetched before the value of \co{p}.
>  This is perhaps easiest to see in the case of value-speculation
>  compiler optimizations, where the compiler guesses the value
> -of \co{p} fetches \co{p->a}, \co{p->b}, and
> -\co{p->c} then fetches the actual value of \co{p}
> +of \co{p}, fetches \co{p->a}, \co{p->b}, and
> +\co{p->c}, and then fetches the actual value of \co{p}
>  in order to check whether its guess was correct.
>  This sort of optimization is quite aggressive, perhaps insanely so,
>  but does actually occur in the context of profile-driven optimization.
> -- 
> 2.7.4
>