linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Zhao Mengmeng <zhaomengmeng@kylinos.cn>,
	akpm@linux-foundation.org, yang@os.amperecomputing.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] mm: gup: add forward declaration for try_grab_folio_fast
Date: Mon, 1 Jul 2024 09:16:14 +0200	[thread overview]
Message-ID: <5b9dafac-1561-4dfa-a0ff-9445cddc0932@redhat.com> (raw)
In-Reply-To: <20240701034052.9988-1-zhaomengmeng@kylinos.cn>

On 01.07.24 05:40, Zhao Mengmeng wrote:
> try_grab_folio_fast() was used in gup_hugepte(), while itself was
> defined after gup_hugepte(), so add a forward declaration to eliminate
> the -Wimplicit-function-declaration warning.
> 
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202407010039.D3sIu3fu-lkp@intel.com/
> Signed-off-by: Zhao Mengmeng <zhaomengmeng@kylinos.cn>
> ---
>   mm/gup.c | 3 +++
>   1 file changed, 3 insertions(+)
> 
> diff --git a/mm/gup.c b/mm/gup.c
> index 7439359d0b71..222b83a87d7d 100644
> --- a/mm/gup.c
> +++ b/mm/gup.c
> @@ -488,6 +488,9 @@ static unsigned long hugepte_addr_end(unsigned long addr, unsigned long end,
>   	return (__boundary - 1 < end - 1) ? __boundary : end;
>   }
>   
> +static struct folio *try_grab_folio_fast(struct page *page, int refs,
> +					 unsigned int flags);
> +

This function should really be called "gup_fast_", just like all other 
gup_fast_ specific functions. I might send some follow-up cleanups later.

-- 
Cheers,

David / dhildenb



  reply	other threads:[~2024-07-01  7:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01  3:40 Zhao Mengmeng
2024-07-01  7:16 ` David Hildenbrand [this message]
2024-07-01  9:23   ` Zhao Mengmeng

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=5b9dafac-1561-4dfa-a0ff-9445cddc0932@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=yang@os.amperecomputing.com \
    --cc=zhaomengmeng@kylinos.cn \
    /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