On Sun, 17 Jul 2016, Akira Yokosawa wrote:
Hi,
On 2016/07/16 16:58:49 +0900, SeongJae Park wrote:
Signed-off-by: SeongJae Park <sj38.park@xxxxxxxxx>
---
defer/whichtochoose.tex | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/defer/whichtochoose.tex b/defer/whichtochoose.tex
index 648cdc8..884de9d 100644
--- a/defer/whichtochoose.tex
+++ b/defer/whichtochoose.tex
@@ -135,7 +135,7 @@ capable of unconditionally acquiring references.
The entry for sequence locks is ``N/A'' because, again, sequence locks
detect updates rather than acquiring references.
Reference counting and hazard pointers require that traversals be
-restarted from the beginning should a given acquisition fail because
+restarted from the beginning if a given acquisition fail because
I can't get the point of this change. Original sentence seems quite natural
for me.
Well, I thought it would be easier to understand the meaning for poor
English speakers like me, though judging is Paul's right. So, please feel
free to discard this patch if you think it's unnecessary, Paul. BTW, I
think I found one trivial grammar mistake here:
`s/a given acquisition fail/a given acquisition fails/`.
the currrent object might be removed and all of its
possible successsors might be not only be removed, but also freed.
For example, when using reference counting or hazard pointers to
However, there are typos here. We need to modify as follows.
-the currrent object might be removed and all of its
-possible successsors might be not only be removed, but also freed.
+the current object might be removed and all of its
+possible successors might be not only be removed, but also freed.
Good catch! 8D It looks like the Many-eyeball law is working well. ;)
Thanks,
SeongJae Park
I'm sorry but I didn't compose in a patch format.
Paul, if you want a proper patch, feel free to ask me.
I'd rather refrain from sending patches that touch Chapter 9, which I assume
is being intensively rewritten right now.
Thanks, Akira
--
To unsubscribe from this list: send the line "unsubscribe perfbook" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
