From: SeongJae Park <sj@kernel.org>
To: paulmck@kernel.org
Cc: SeongJae Park <sj38.park@gmail.com>, perfbook@vger.kernel.org
Subject: [PATCH 00/12] formal: Trivial fixups
Date: Sat, 8 Apr 2023 10:32:57 -0700 [thread overview]
Message-ID: <20230408173309.5543-1-sj@kernel.org> (raw)
From: SeongJae Park <sj38.park@gmail.com>
This patchset contains trivial fixups for formal/, which found from
its Korean translation[1].
[1] https://github.com/sjp38/perfbook-ko_KR
SeongJae Park (12):
formal/formal: Drop cppmem from 'Special-Purpose State-Space Search'
section explanation
formal/spinhint: Use \qco{} instead of ``\co{}''
formal/spinhint: Enclose example code snippets with \co{}
formal/spinhint: Do not call 2013 paper as recent
formal/dyntickrcu: Quote 'trail' file consistently
formal/dyntickrcu: Use \qco{} instead of ``\co{}''
formal/ppcmem: Use uppercase 'S' for Spin
formal/ppcmem: Use \qco{} instead of ``\co{}''
formal/ppcmem: Add missed non-breakable spaces
formal/ppcmem: Enclose example code snippets with \co{}
formal/ppcmem: s/powerpc/PowerPC/ on sentences
formal/ppcmem: Fix label name for Fail1:
formal/axiomatic.tex | 30 +++++++++++++++---------------
formal/dyntickrcu.tex | 10 +++++-----
formal/formal.tex | 2 +-
formal/ppcmem.tex | 26 +++++++++++++-------------
formal/spinhint.tex | 16 ++++++++--------
5 files changed, 42 insertions(+), 42 deletions(-)
--
2.17.1
next reply other threads:[~2023-04-08 17:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-08 17:32 SeongJae Park [this message]
2023-04-08 17:32 ` [PATCH 01/12] formal/formal: Drop cppmem from 'Special-Purpose State-Space Search' section explanation SeongJae Park
2023-04-08 17:32 ` [PATCH 02/12] formal/spinhint: Use \qco{} instead of ``\co{}'' SeongJae Park
2023-04-08 17:33 ` [PATCH 03/12] formal/spinhint: Enclose example code snippets with \co{} SeongJae Park
2023-04-08 17:33 ` [PATCH 04/12] formal/spinhint: Do not call 2013 paper as recent SeongJae Park
2023-04-08 17:33 ` [PATCH 05/12] formal/dyntickrcu: Quote 'trail' file consistently SeongJae Park
2023-04-08 17:33 ` [PATCH 06/12] formal/dyntickrcu: Use \qco{} instead of ``\co{}'' SeongJae Park
2023-04-08 17:33 ` [PATCH 07/12] formal/ppcmem: Use uppercase 'S' for Spin SeongJae Park
2023-04-08 17:33 ` [PATCH 08/12] formal/ppcmem: Use \qco{} instead of ``\co{}'' SeongJae Park
2023-04-08 17:33 ` [PATCH 09/12] formal/ppcmem: Add missed non-breakable spaces SeongJae Park
2023-04-08 17:33 ` [PATCH 10/12] formal/ppcmem: Enclose example code snippets with \co{} SeongJae Park
2023-04-08 17:33 ` [PATCH 11/12] formal/ppcmem: s/powerpc/PowerPC/ on sentences SeongJae Park
2023-04-08 17:33 ` [PATCH 12/12] formal/ppcmem: Fix label name for Fail1: SeongJae Park
2023-04-10 2:42 ` [PATCH 00/12] formal: Trivial fixups 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=20230408173309.5543-1-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.