linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Mel Gorman <mgorman@suse.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH] mm: fix filemap.c pagecache_get_page() kernel-doc warnings
Date: Mon, 28 Jul 2014 08:27:48 -0700	[thread overview]
Message-ID: <53D66BF4.1070200@infradead.org> (raw)
In-Reply-To: <20140728093630.GM10819@suse.de>

On 07/28/14 02:36, Mel Gorman wrote:
> On Sun, Jul 27, 2014 at 01:45:33PM -0700, Randy Dunlap wrote:
>> From: Randy Dunlap <rdunlap@infradead.org>
>>
>> Fix kernel-doc warnings in mm/filemap.c: pagecache_get_page():
>>
>> Warning(..//mm/filemap.c:1054): No description found for parameter 'cache_gfp_mask'
>> Warning(..//mm/filemap.c:1054): No description found for parameter 'radix_gfp_mask'
>> Warning(..//mm/filemap.c:1054): Excess function parameter 'gfp_mask' description in 'pagecache_get_page'
>>
>> Fixes: 2457aec63745 "mm: non-atomically mark page accessed during
>> 	page cache allocation where possible"
>>
>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>> Cc: Mel Gorman <mgorman@suse.de>
> 
> Use this diff instead?

Sure.  Acked-by: Randy Dunlap <rdunlap@infradead.org>

Thanks.

Andrew?

> 
> ---8<---
> diff --git a/mm/filemap.c b/mm/filemap.c
> index dafb06f..a1021fa 100644
> --- a/mm/filemap.c
> +++ b/mm/filemap.c
> @@ -1031,18 +1031,21 @@ EXPORT_SYMBOL(find_lock_entry);
>   * @mapping: the address_space to search
>   * @offset: the page index
>   * @fgp_flags: PCG flags
> - * @gfp_mask: gfp mask to use if a page is to be allocated
> + * @cache_gfp_mask: gfp mask to use for the page cache data page allocation
> + * @radix_gfp_mask: gfp mask to use for radix tree node allocation
>   *
>   * Looks up the page cache slot at @mapping & @offset.
>   *
> - * PCG flags modify how the page is returned
> + * PCG flags modify how the page is returned.
>   *
>   * FGP_ACCESSED: the page will be marked accessed
>   * FGP_LOCK: Page is return locked
>   * FGP_CREAT: If page is not present then a new page is allocated using
> - *		@gfp_mask and added to the page cache and the VM's LRU
> - *		list. The page is returned locked and with an increased
> - *		refcount. Otherwise, %NULL is returned.
> + *		@cache_gfp_mask and added to the page cache and the VM's LRU
> + *		list. If radix tree nodes are allocated during page cache
> + *		insertion then @radix_gfp_mask is used. The page is returned
> + * 		locked and with an increased refcount. Otherwise, %NULL is
> + * 		returned.
>   *
>   * If FGP_LOCK or FGP_CREAT are specified then the function may sleep even
>   * if the GFP flags specified for FGP_CREAT are atomic.
> 


-- 
~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>

      reply	other threads:[~2014-07-28 15:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-27 20:45 [PATCH] mm: fix filemap.c pagecache_get_page() kernel-doc warnings Randy Dunlap
2014-07-28  9:36 ` Mel Gorman
2014-07-28 15:27   ` 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=53D66BF4.1070200@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=torvalds@linux-foundation.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).