From: David Howells <dhowells@redhat•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: dhowells@redhat•com,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: linux-next: build warning after merge of the fscache tree
Date: Tue, 30 Nov 2021 11:18:46 +0000 [thread overview]
Message-ID: <429852.1638271126@warthog.procyon.org.uk> (raw)
In-Reply-To: <20211130175119.63d0e7aa@canb.auug.org.au>
Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> Documentation/filesystems/netfs_library.rst:518: WARNING: Inline emphasis start-string without end-string.
> Documentation/filesystems/netfs_library.rst:518: WARNING: Inline emphasis start-string without end-string.
Ah... I worked out what that's about. It's not actually on the line
specified, but rather later in the same paragraph:
the write. *_start and *_len indicate the region to be written; the region
with the two asterisks. I guess wrapping them like:
the write. ``*_start`` and ``*_len`` indicate the region to be written; the
might be the right thing to do.
David
next prev parent reply other threads:[~2021-11-30 11:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 5:23 linux-next: build warning after merge of the fscache tree Stephen Rothwell
2021-11-30 6:51 ` Stephen Rothwell
2021-11-30 11:18 ` David Howells [this message]
2021-11-30 11:13 ` David Howells
-- strict thread matches above, loose matches on Subject: below --
2022-03-03 9:28 Stephen Rothwell
2021-12-20 11:46 Stephen Rothwell
2021-11-30 4:27 Stephen Rothwell
2021-12-06 7:08 ` Stephen Rothwell
2021-10-05 9:46 Stephen Rothwell
2021-10-21 1:29 ` Stephen Rothwell
2021-10-21 14:32 ` David Howells
2021-10-21 23:15 ` Stephen Rothwell
2021-03-03 6:07 Stephen Rothwell
2021-03-02 22:16 Stephen Rothwell
2021-03-02 22:48 ` David Howells
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=429852.1638271126@warthog.procyon.org.uk \
--to=dhowells@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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