From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
To: Linux Doc Mailing List <linux-doc@vger.kernel.org>
Cc: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Theodore Ts'o" <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 10/16] docs: filesystems: ext4: blockgroup.rst: replace some characters
Date: Sun, 16 May 2021 12:18:27 +0200 [thread overview]
Message-ID: <5457dec1f5acbd168e7eead268541cadb2d8018c.1621159997.git.mchehab+huawei@kernel.org> (raw)
In-Reply-To: <cover.1621159997.git.mchehab+huawei@kernel.org>
The conversion tools used during DocBook/LaTeX/html/Markdown->ReST
conversion and some cut-and-pasted text contain some characters that
aren't easily reachable on standard keyboards and/or could cause
troubles when parsed by the documentation build system.
Replace the occurences of the following characters:
- U+2217 ('∗'): ASTERISK OPERATOR
use ASCII asterisk instead of the ASTERISK OPERATOR
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
---
Documentation/filesystems/ext4/blockgroup.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/filesystems/ext4/blockgroup.rst b/Documentation/filesystems/ext4/blockgroup.rst
index 3da156633339..d5d652addce5 100644
--- a/Documentation/filesystems/ext4/blockgroup.rst
+++ b/Documentation/filesystems/ext4/blockgroup.rst
@@ -84,7 +84,7 @@ Without the option META\_BG, for safety concerns, all block group
descriptors copies are kept in the first block group. Given the default
128MiB(2^27 bytes) block group size and 64-byte group descriptors, ext4
can have at most 2^27/64 = 2^21 block groups. This limits the entire
-filesystem size to 2^21 ∗ 2^27 = 2^48bytes or 256TiB.
+filesystem size to 2^21 * 2^27 = 2^48bytes or 256TiB.
The solution to this problem is to use the metablock group feature
(META\_BG), which is already in ext3 for all 2.6 releases. With the
--
2.31.1
next prev parent reply other threads:[~2021-05-16 10:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-16 10:18 [PATCH v3 00/16] Replace some bad characters on documents Mauro Carvalho Chehab
2021-05-16 10:18 ` [PATCH v3 01/16] docs: hwmon: ir36021.rst: replace some characters Mauro Carvalho Chehab
2021-05-16 10:18 ` [PATCH v3 02/16] docs: admin-guide: reporting-issues.rst: " Mauro Carvalho Chehab
2021-05-16 10:28 ` Thorsten Leemhuis
2021-05-16 11:13 ` Mauro Carvalho Chehab
2021-05-16 10:18 ` [PATCH v3 03/16] docs: trace: coresight: coresight-etm4x-reference.rst: " Mauro Carvalho Chehab
2021-05-16 10:18 ` [PATCH v3 04/16] docs: driver-api: ioctl.rst: " Mauro Carvalho Chehab
2021-05-16 10:18 ` [PATCH v3 05/16] docs: driver-api: media: drivers: zoran.rst: " Mauro Carvalho Chehab
2021-05-16 18:32 ` LABBE Corentin
2021-05-16 10:18 ` [PATCH v3 06/16] docs: usb: " Mauro Carvalho Chehab
2021-05-16 10:18 ` [PATCH v3 07/16] docs: userspace-api: media: v4l: dev-decoder.rst: " Mauro Carvalho Chehab
2021-05-16 10:18 ` [PATCH v3 08/16] docs: userspace-api: media: dvb: intro.rst: " Mauro Carvalho Chehab
2021-05-16 10:18 ` [PATCH v3 09/16] docs: vm: zswap.rst: " Mauro Carvalho Chehab
2021-05-16 10:18 ` Mauro Carvalho Chehab [this message]
2021-05-16 10:18 ` [PATCH v3 11/16] docs: networking: device_drivers: " Mauro Carvalho Chehab
2021-05-17 16:11 ` Jesse Brandeburg
2021-05-16 10:18 ` [PATCH v3 12/16] docs: PCI: acpi-info.rst: " Mauro Carvalho Chehab
2021-05-19 21:47 ` Bjorn Helgaas
2021-06-16 6:51 ` Mauro Carvalho Chehab
2021-05-16 10:18 ` [PATCH v3 13/16] docs: sound: kernel-api: writing-an-alsa-driver.rst: " Mauro Carvalho Chehab
2021-05-16 10:18 ` [PATCH v3 14/16] docs: firmware-guide: acpi: dsd: graph.rst: " Mauro Carvalho Chehab
2021-05-17 14:20 ` Rafael J. Wysocki
2021-05-16 10:18 ` [PATCH v3 15/16] docs: virt: kvm: api.rst: " Mauro Carvalho Chehab
2021-05-16 10:18 ` [PATCH v3 16/16] docs: RCU: " Mauro Carvalho Chehab
2021-05-17 10:53 ` Akira Yokosawa
2021-05-17 10:48 ` [PATCH v3 00/16] Replace some bad characters on documents David Woodhouse
2021-05-17 11:24 ` Mauro Carvalho Chehab
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=5457dec1f5acbd168e7eead268541cadb2d8018c.1621159997.git.mchehab+huawei@kernel.org \
--to=mchehab+huawei@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).