From: Randy Dunlap <rdunlap@infradead.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Linux MM <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH] mm/swap.c: fix kernel-doc functions and parameters
Date: Mon, 29 Jan 2018 15:54:39 -0800 [thread overview]
Message-ID: <9e3a965a-eceb-a9c2-9277-68231077c146@infradead.org> (raw)
In-Reply-To: <20180129051532.GA18247@bombadil.infradead.org>
On 01/28/2018 09:15 PM, Matthew Wilcox wrote:
> On Sun, Jan 28, 2018 at 08:01:08PM -0800, Randy Dunlap wrote:
>> @@ -400,6 +400,10 @@ void mark_page_accessed(struct page *pag
>> }
>> EXPORT_SYMBOL(mark_page_accessed);
>>
>> +/**
>> + * __lru_cache_add: add a page to the page lists
>> + * @page: the page to add
>> + */
>> static void __lru_cache_add(struct page *page)
>> {
>> struct pagevec *pvec = &get_cpu_var(lru_add_pvec);
>> @@ -410,10 +414,6 @@ static void __lru_cache_add(struct page
>> put_cpu_var(lru_add_pvec);
>> }
>>
>> -/**
>> - * lru_cache_add: add a page to the page lists
>> - * @page: the page to add
>> - */
>> void lru_cache_add_anon(struct page *page)
>> {
>> if (PageActive(page))
>
> I don't see the point in adding kernel-doc for a static function while
> deleting it for a non-static function? I'd change the name of the
> function in the second hunk and drop the first hunk.
Agree.
> Also, the comment doesn't actually fit the kernel-doc format (colon
> versus hyphen; missing capitalisation and full-stop).
I certainly missed the colon vs. hyphen. But I am not aware of any kernel-doc
format about capitalization or ending with a period -- and don't like them either.
Those descriptions usually are not complete sentences unless they are longer
descriptions.
>> @@ -913,11 +913,11 @@ EXPORT_SYMBOL(__pagevec_lru_add);
>> * @pvec: Where the resulting entries are placed
>> * @mapping: The address_space to search
>> * @start: The starting entry index
>> - * @nr_entries: The maximum number of entries
>> + * @nr_pages: The maximum number of entries
>> * @indices: The cache indices corresponding to the entries in @pvec
>> *
>> * pagevec_lookup_entries() will search for and return a group of up
>> - * to @nr_entries pages and shadow entries in the mapping. All
>> + * to @nr_pages pages and shadow entries in the mapping. All
>> * entries are placed in @pvec. pagevec_lookup_entries() takes a
>> * reference against actual pages in @pvec.
>> *
>
> I think the documentation has the right name here; it is the number of
> entries and not the number of pages which is returned. We should change
> the code to match the documentation here ;-)
OK, will change that and send v2.
Thanks for the comments.
--
~Randy
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2018-01-29 23:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 4:01 [PATCH] mm/swap.c: fix kernel-doc functions and parameters Randy Dunlap
2018-01-29 5:15 ` Matthew Wilcox
2018-01-29 23:54 ` Randy Dunlap [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=9e3a965a-eceb-a9c2-9277-68231077c146@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).