From: David Howells <dhowells@redhat.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: dhowells@redhat.com, linux-cachefs@redhat.com,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
Matthew Wilcox <willy@infradead.org>
Subject: Re: [Linux-cachefs] [PATCH] netfs: Adjust docs after foliation
Date: Mon, 29 Nov 2021 15:23:34 +0000 [thread overview]
Message-ID: <223020.1638199414@warthog.procyon.org.uk> (raw)
In-Reply-To: <2cfdbfd834bb6ff1f7f5cf47e3ea72449fe683b6.camel@redhat.com>
Jeff Layton <jlayton@redhat.com> wrote:
> > -/**
> > - * netfs_skip_folio_read - prep a folio for writing without reading first
> > +/*
> ...
> Not sure why you decided to change the last one not to be a kerneldoc
> comment, but OK. The rest of the changes look straightforward.
It's not part of the API. It's only internal. None of the other internal
functions are listed in the API reference.
David
prev parent reply other threads:[~2021-11-29 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 13:38 David Howells
2021-11-29 14:31 ` [Linux-cachefs] " Jeff Layton
2021-11-29 15:23 ` David Howells [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=223020.1638199414@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=jlayton@redhat.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=willy@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