public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: David Howells <dhowells@redhat•com>
Cc: 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: Fri, 22 Oct 2021 10:15:16 +1100	[thread overview]
Message-ID: <20211022101516.7877fa7f@canb.auug.org.au> (raw)
In-Reply-To: <738109.1634826774@warthog.procyon.org.uk>

[-- Attachment #1: Type: text/plain, Size: 488 bytes --]

Hi David,

On Thu, 21 Oct 2021 15:32:54 +0100 David Howells <dhowells@redhat•com> wrote:
>
> Stephen Rothwell <sfr@canb•auug.org.au> wrote:
> 
> > > Documentation/filesystems/caching/backend-api.rst:402: WARNING: Inline emphasis start-string without end-string.  
> 
> I'm not sure what that even means.

I assume it is referring to the "*cres" with on ending "*" ... I am not
sure how to quote the "*".  Maybe just with \ ... or ``*cres`` ?

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2021-10-21 23:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05  9:46 linux-next: build warning after merge of the fscache tree Stephen Rothwell
2021-10-21  1:29 ` Stephen Rothwell
2021-10-21 14:32   ` David Howells
2021-10-21 23:15     ` Stephen Rothwell [this message]
  -- 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  5:23 Stephen Rothwell
2021-11-30  6:51 ` Stephen Rothwell
2021-11-30 11:18   ` David Howells
2021-11-30 11:13 ` David Howells
2021-11-30  4:27 Stephen Rothwell
2021-12-06  7:08 ` 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=20211022101516.7877fa7f@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=dhowells@redhat$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    /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