All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Johann Klähn" <johann@jklaehn.de>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: perfbook@vger.kernel.org
Subject: [PATCH-perfbook 4/4] glossary: Use more common definition of RAII
Date: Tue,  1 Feb 2022 21:07:51 +0100	[thread overview]
Message-ID: <20220201200751.23589-4-johann@jklaehn.de> (raw)
In-Reply-To: <20220201200751.23589-1-johann@jklaehn.de>

Cf. https://en.cppreference.com/w/cpp/language/raii or
https://en.wikipedia.org/wiki/Resource_acquisition_is_initialization.

Signed-off-by: Johann Klähn <johann@jklaehn.de>
---
 glsdict.tex | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/glsdict.tex b/glsdict.tex
index 194f364d..d1468859 100644
--- a/glsdict.tex
+++ b/glsdict.tex
@@ -237,8 +237,8 @@
 \newacronym{numa}{NUMA}{non-uniform memory architecture}
 \newacronym{qsbr}{QSBR}{quiescent-state-based reclamation}
 \newabbreviation{qsbr:m}{QSBR}{quiescent-state-based-reclamation}
-\newacronym{raii}{RAII}{resource allocation is initialization}
-\newabbreviation{raii:m}{RAII}{resource-allocation-is-initialization}
+\newacronym{raii}{RAII}{resource acquisition is initialization}
+\newabbreviation{raii:m}{RAII}{resource-acquisition-is-initialization}
 \newacronym{rcu}{RCU}{read-copy update}
 \newacronym{smp}{SMP}{symmetric multiprocessing}
 \newabbreviation{smp:m}{SMP}{symmetric-multiprocessing}
-- 
2.34.1


  parent reply	other threads:[~2022-02-01 20:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01 20:07 [PATCH-perfbook 1/4] cpu: Fix typo Johann Klähn
2022-02-01 20:07 ` [PATCH-perfbook 2/4] defer: Remove leftover manipulation of bottom bit in hazptr.c Johann Klähn
2022-02-01 20:07 ` [PATCH-perfbook 3/4] glossary: Fix typo Johann Klähn
2022-02-01 20:07 ` Johann Klähn [this message]
2022-02-01 20:38   ` [PATCH-perfbook 4/4] glossary: Use more common definition of RAII Paul E. McKenney
2022-02-01 22:16     ` Johann Klähn
2022-02-03 23:34       ` Paul E. McKenney

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=20220201200751.23589-4-johann@jklaehn.de \
    --to=johann@jklaehn.de \
    --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.