All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: perfbook@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: [PATCH 3/3] intro: Fix typo
Date: Fri, 17 Jan 2020 07:00:30 +0900	[thread overview]
Message-ID: <cbe1f7ea-d39a-47c9-13a8-32f5ce96c38e@gmail.com> (raw)
In-Reply-To: <805bd7c5-477f-c398-b025-34a630f663f9@gmail.com>

From 865d0b46e811f6a719f4af1a59d65c6f70185108 Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <akiyks@gmail.com>
Date: Mon, 13 Jan 2020 19:51:52 +0900
Subject: [PATCH 3/3] intro: Fix typo

Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
---
 intro/intro.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/intro/intro.tex b/intro/intro.tex
index beda0464..e3ec3a43 100644
--- a/intro/intro.tex
+++ b/intro/intro.tex
@@ -361,7 +361,7 @@ which shows that writing single-threaded code and simply waiting
 a year or two for the CPUs to catch up may no longer be an option.
 Given the recent trends on the part of all major manufacturers towards
 multicore/multithreaded systems, parallelism is the way to go for
-those wanting the avail themselves of the full performance of their
+those wanting to avail themselves of the full performance of their
 systems.
 
 Even so, the first goal is performance rather than scalability,
-- 
2.17.1



      parent reply	other threads:[~2020-01-16 22:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16 21:54 [PATCH 0/3] Fix for Fedora31 Akira Yokosawa
2020-01-16 21:57 ` [PATCH 1/3] utilities/fixsvgfonts-urwps.sh: Use symbol font available on F31 Akira Yokosawa
2020-01-16 21:59 ` [PATCH 2/3] howto: Fix typo Akira Yokosawa
2020-01-17  3:36   ` Paul E. McKenney
2020-01-18 10:52     ` Akira Yokosawa
2020-01-18 19:42       ` Paul E. McKenney
2020-01-18 23:11         ` Akira Yokosawa
2020-01-19  5:46           ` Paul E. McKenney
2020-01-16 22:00 ` Akira Yokosawa [this message]

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=cbe1f7ea-d39a-47c9-13a8-32f5ce96c38e@gmail.com \
    --to=akiyks@gmail.com \
    --cc=paulmck@kernel.org \
    --cc=perfbook@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.