linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
To: Randy Dunlap <rdunlap@infradead.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: "linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: procfs VmFlags table missing from online docs
Date: Tue, 14 Jul 2020 08:45:25 +0000	[thread overview]
Message-ID: <a8747dde-32d8-bbfd-fe73-662827abd60e@alliedtelesis.co.nz> (raw)
In-Reply-To: <6ee41c18-934e-26c2-a875-3d9e4c700c6c@infradead.org>


On 14/07/20 6:06 pm, Randy Dunlap wrote:
> On 7/13/20 10:11 PM, Chris Packham wrote:
>> Hi,
>>
>> I was just browsing
>> https://www.kernel.org/doc/html/latest/filesystems/proc.html
>>
>> The "VmFlags" description seems to be missing a table. It's there in
>> Documentation/filesystems/proc.rst so I assume it's some sphinx/rst
>> problem. Possibly the table is over indented?
> Wow. It skips the table completely.
>
> I tried a couple of things that did not help.
I think it's just the stray - in the "bt - arm64" line patch incoming.
>> Anyway I thought I'd let someone know.
> Thanks.
>
>> Regards,
>> Chris
>

      reply	other threads:[~2020-07-14  9:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-14  5:11 procfs VmFlags table missing from online docs Chris Packham
2020-07-14  6:06 ` Randy Dunlap
2020-07-14  8:45   ` Chris Packham [this message]

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=a8747dde-32d8-bbfd-fe73-662827abd60e@alliedtelesis.co.nz \
    --to=chris.packham@alliedtelesis.co.nz \
    --cc=adobriyan@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=rdunlap@infradead.org \
    /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).