From: Dave Chinner <david@fromorbit.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Randy Dunlap <rdunlap@infradead.org>,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH v2] doc: document scope NOFS, NOIO APIs
Date: Tue, 29 May 2018 20:22:15 +1000 [thread overview]
Message-ID: <20180529102215.GL23861@dastard> (raw)
In-Reply-To: <20180529082644.26192-1-mhocko@kernel.org>
On Tue, May 29, 2018 at 10:26:44AM +0200, Michal Hocko wrote:
> From: Michal Hocko <mhocko@suse.com>
>
> Although the api is documented in the source code Ted has pointed out
> that there is no mention in the core-api Documentation and there are
> people looking there to find answers how to use a specific API.
>
> Changes since v1
> - add kerneldoc for the api - suggested by Johnatan
> - review feedback from Dave and Johnatan
> - feedback from Dave about more general critical context rather than
> locking
> - feedback from Mike
> - typo fixed - Randy, Dave
>
> Requested-by: "Theodore Y. Ts'o" <tytso@mit.edu>
> Signed-off-by: Michal Hocko <mhocko@suse.com>
We could bikeshed forever about the exact wording, but it covers
everything I think needs to be documented.
Reviewed-by: Dave Chinner <dchinner@redhat.com>
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2018-05-29 10:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180424183536.GF30619@thunk.org>
2018-05-24 11:43 ` [PATCH] doc: document scope NOFS, NOIO APIs Michal Hocko
2018-05-24 14:33 ` Shakeel Butt
2018-05-24 14:47 ` Michal Hocko
2018-05-24 16:37 ` Randy Dunlap
2018-05-25 7:52 ` Michal Hocko
2018-05-28 7:21 ` Nikolay Borisov
2018-05-29 8:22 ` Michal Hocko
2018-05-28 11:32 ` Vlastimil Babka
2018-05-24 20:52 ` Jonathan Corbet
2018-05-25 8:11 ` Michal Hocko
2018-05-24 22:17 ` Dave Chinner
2018-05-24 23:25 ` Theodore Y. Ts'o
2018-05-25 8:16 ` Michal Hocko
2018-05-27 12:47 ` Mike Rapoport
2018-05-28 9:21 ` Michal Hocko
2018-05-28 16:10 ` Randy Dunlap
2018-05-29 8:21 ` Michal Hocko
2018-05-27 23:48 ` Dave Chinner
2018-05-28 9:19 ` Michal Hocko
2018-05-28 22:32 ` Dave Chinner
2018-05-29 8:18 ` Michal Hocko
2018-05-29 8:26 ` [PATCH v2] " Michal Hocko
2018-05-29 10:22 ` Dave Chinner [this message]
2018-05-29 11:50 ` Mike Rapoport
2018-05-29 11:51 ` Jonathan Corbet
2018-05-29 12:37 ` Michal Hocko
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=20180529102215.GL23861@dastard \
--to=david@fromorbit.com \
--cc=corbet@lwn.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mhocko@suse.com \
--cc=rdunlap@infradead.org \
--cc=rppt@linux.vnet.ibm.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).