From: Zhao Mengmeng <zhaomengmeng@kylinos.cn>
To: David Hildenbrand <david@redhat.com>,
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 17:23:40 +0800 [thread overview]
Message-ID: <1141ee04-1466-d1c5-e2b7-8512e9f8f78c@kylinos.cn> (raw)
In-Reply-To: <5b9dafac-1561-4dfa-a0ff-9445cddc0932@redhat.com>
On 2024/7/1 15:16, David Hildenbrand wrote:
> 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.
>
Yeah, looking forward to your patch. Besides, I have seen Yang's fix in
https://lore.kernel.org/linux-mm/CAHbLzkowMSso-4Nufc9hcMehQsK9PNz3OSu-+eniU-2Mm-xjhA@mail.gmail.com/T/#m7ff03bf88814d8352052fbd8a1c90fee0ba5b576
and it is better. So sorry to bother you all.
prev parent reply other threads:[~2024-07-01 9:23 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
2024-07-01 9:23 ` Zhao Mengmeng [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=1141ee04-1466-d1c5-e2b7-8512e9f8f78c@kylinos.cn \
--to=zhaomengmeng@kylinos.cn \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=yang@os.amperecomputing.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