All of lore.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: paulmck@kernel.org
Cc: perfbook@vger.kernel.org, SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH 1/4] datastruct: Remove unnecessary space
Date: Mon, 26 Dec 2022 10:16:31 -0800	[thread overview]
Message-ID: <20221226181639.10795-2-sj@kernel.org> (raw)
In-Reply-To: <20221226181639.10795-1-sj@kernel.org>

From: SeongJae Park <sj38.park@gmail.com>

A sentence in datastruct has unnecessary extra space between words.
Remove it.

Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
 datastruct/datastruct.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/datastruct/datastruct.tex b/datastruct/datastruct.tex
index ed404e5a..99c92d9a 100644
--- a/datastruct/datastruct.tex
+++ b/datastruct/datastruct.tex
@@ -34,7 +34,7 @@ which improves both performance and scalability.
 Because this chapter cannot delve into the details of every concurrent
 data structure,
 \cref{sec:datastruct:Other Data Structures}
-surveys a few  of the important ones.
+surveys a few of the important ones.
 Although the best performance and scalability results from design rather
 than after-the-fact micro-optimization, micro-optimization is nevertheless
 necessary for the absolute best possible performance and scalability,
-- 
2.17.1


  reply	other threads:[~2022-12-26 18:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-26 18:16 [PATCH 0/4] datastruct: Minor fixes SeongJae Park
2022-12-26 18:16 ` SeongJae Park [this message]
2022-12-26 18:16 ` [PATCH 2/4] datastruct: Add missed unbreakable spaces SeongJae Park
2022-12-26 23:41   ` Akira Yokosawa
2022-12-27  0:26     ` Paul E. McKenney
2022-12-27 16:04       ` SeongJae Park
2022-12-27 16:06       ` [PATCH v2] " SeongJae Park
2022-12-27 16:06         ` SeongJae Park
2022-12-27 18:29           ` Paul E. McKenney
2022-12-27 23:26             ` Akira Yokosawa
2022-12-28  0:40               ` Paul E. McKenney
2022-12-26 18:16 ` [PATCH 3/4] datastruct: Enclose NULL with \co{} SeongJae Park
2022-12-26 18:16 ` [PATCH 4/4] datastruct: Put \cref{} content in a single line SeongJae Park
2022-12-26 18:16 ` [PATCH 0/4] datastruct: Minor fixes SeongJae Park
2022-12-26 18:16 ` [PATCH 1/4] datastruct: Remove unnecessary space SeongJae Park
2022-12-26 18:16 ` [PATCH 2/4] datastruct: Add missed unbreakable spaces SeongJae Park
2022-12-26 18:16 ` [PATCH 3/4] datastruct: Enclose NULL with \co{} SeongJae Park
2022-12-26 18:16 ` [PATCH 4/4] datastruct: Put \cref{} content in a single line SeongJae Park

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=20221226181639.10795-2-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=paulmck@kernel.org \
    --cc=perfbook@vger.kernel.org \
    --cc=sj38.park@gmail.com \
    /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.