Linux-Fsdevel Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Hugh Dickins <firstname.lastname@example.org>
To: Randy Dunlap <email@example.com>
Cc: Hugh Dickins <firstname.lastname@example.org>,
Andrew Morton <email@example.com>,
Chris Down <firstname.lastname@example.org>,
Al Viro <email@example.com>,
Matthew Wilcox <firstname.lastname@example.org>,
Amir Goldstein <email@example.com>,
Jeff Layton <firstname.lastname@example.org>,
Johannes Weiner <email@example.com>, Tejun Heo <firstname.lastname@example.org>,
Subject: Re: [PATCH mmotm] tmpfs: support 64-bit inums per-sb fix
Date: Sat, 1 Aug 2020 22:25:34 -0700 (PDT) [thread overview]
Message-ID: <alpine.LSU.email@example.com> (raw)
On Sat, 1 Aug 2020, Randy Dunlap wrote:
> On 8/1/20 7:37 PM, Hugh Dickins wrote:
> > Expanded Chris's Documentation and Kconfig help on tmpfs inode64.
> > TMPFS_INODE64 still there, still default N, but writing down its very
> > limited limitation does make me wonder again if we want the option.
> > Signed-off-by: Hugh Dickins <firstname.lastname@example.org>
> > ---
> > Andrew, please fold into tmpfs-support-64-bit-inums-per-sb.patch later.
> > Randy, you're very active on Documentation and linux-next: may I ask you
> > please to try applying this patch to latest, and see if tmpfs.rst comes
> > out looking right to you? I'm an old dog still stuck in the days of
> Hi Hugh,
> It looks fine.
Thank you so much, Randy.
> > tmpfs.txt, hoping to avoid new tricks for a while. Thanks! (Bonus
> > points if you can explain what the "::" on line 122 is about. I started
> > out reading Documentation/doc-guide/sphinx.rst, but... got diverted.
> > Perhaps I should ask Mauro or Jon, but turning for help first to you.)
> That's the correct file. Around line 216, it says:
> * For inserting fixed width text blocks (for code examples, use case
> examples, etc.), use ``::`` for anything that doesn't really benefit
> from syntax highlighting, especially short snippets. Use
> ``.. code-block:: <language>`` for longer code blocks that benefit
> from highlighting. For a short snippet of code embedded in the text, use \`\`.
> so it's just for a (short) code example block, fixed font...
Bonus points awarded, thanks...ish. I'll have to look around for more
examples of where that's done, and I think it'll only make real sense
to me, when I'm further along, producing the proper output, then seeing
how bad something looks without the "::".
prev parent reply other threads:[~2020-08-02 5:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 17:28 [PATCH v7 0/2] tmpfs: inode: Reduce risk of inum overflow Chris Down
2020-07-13 17:28 ` [PATCH v7 1/2] tmpfs: Per-superblock i_ino support Chris Down
2020-08-01 19:22 ` Hugh Dickins
2020-07-13 17:28 ` [PATCH v7 2/2] tmpfs: Support 64-bit inums per-sb Chris Down
2020-08-01 20:41 ` Hugh Dickins
2020-08-02 2:37 ` [PATCH mmotm] tmpfs: support 64-bit inums per-sb fix Hugh Dickins
2020-08-02 3:05 ` Randy Dunlap
2020-08-02 5:25 ` Hugh Dickins [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--subject='Re: [PATCH mmotm] tmpfs: support 64-bit inums per-sb fix' \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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).