From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
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 08:42:34 +0200 [thread overview]
Message-ID: <20180710064234.GA2053@kroah.com> (raw)
In-Reply-To: <20180709151248.2e124971e8af515fd95b9319@linux-foundation.org>
On Mon, Jul 09, 2018 at 03:12:48PM -0700, Andrew Morton wrote:
> On Mon, 9 Jul 2018 15:00:17 -0700 (PDT) David Rientjes <rientjes@google.com> wrote:
>
> > There is no canonical location for debugfs docuemntation, so start one.
What is wrong with Documenation/filesystems/debugfs.txt?
> > This is primarily motivated to describe the oom_free_timeout_ms interface
> > but it is extended for all the debugfs files that I am personally
> > interested in.
> >
> > Hopefully this can be expanded in the future for better insight into how
> > the various interfaces can be used.
Ah, you are talking about the contents of debugfs files, right? Just
use Documenation/ABI/ if you really want to document these things. But
really, it's debugfs, so things can, and will, change, you should never
build tools that rely on the specific information contained in those
files.
thanks,
greg k-h
--
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 6:42 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 [this message]
2018-07-10 6:45 ` Greg KH
2018-07-10 11:28 ` Jonathan Corbet
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=20180710064234.GA2053@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--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).