From: Jonathan Corbet <corbet@lwn.net>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] docs, debugfs: start explicit debugfs documentation
Date: Tue, 10 Jul 2018 05:28:35 -0600 [thread overview]
Message-ID: <20180710052835.581cdf28@lwn.net> (raw)
In-Reply-To: <20180710064506.GA2316@kroah.com>
On Tue, 10 Jul 2018 08:45:06 +0200
Greg KH <gregkh@linuxfoundation.org> wrote:
> For the "this is what a specific debugfs file contains", those should go
> into Documenation/ABI/ if you really want to document those types of
> things.
Do we really want to start populating Documentation/ABI with stuff that's
explicitly *not* ABI? Keeping it separate might make more sense, IMO.
I'd put extfrag_index with the MM docs, for example.
> But as it is, this single patch does too many different things all at
> once.
...and yet not enough :) This stuff is almost in RST already, it would
be nice to go all the way and integrate it into the rest of our docs.
Thanks,
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-07-10 11:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 22:00 [patch] docs, debugfs: start explicit debugfs documentation David Rientjes
2018-07-09 22:12 ` Andrew Morton
2018-07-10 6:42 ` Greg Kroah-Hartman
2018-07-10 6:45 ` Greg KH
2018-07-10 11:28 ` Jonathan Corbet [this message]
2018-07-10 11:46 ` Greg KH
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=20180710052835.581cdf28@lwn.net \
--to=corbet@lwn.net \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.org \
--cc=rientjes@google.com \
/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).