From: Matthew Wilcox <willy@infradead.org>
To: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Abaci Robot <abaci@linux.alibaba.com>
Subject: Re: [PATCH] mempool: Modify mismatched function name
Date: Fri, 29 Mar 2024 03:22:48 +0000 [thread overview]
Message-ID: <ZgY0CGZGgV7kgehP@casper.infradead.org> (raw)
In-Reply-To: <20240329030118.68492-1-jiapeng.chong@linux.alibaba.com>
On Fri, Mar 29, 2024 at 11:01:18AM +0800, Jiapeng Chong wrote:
> No functional modification involved.
>
> mm/mempool.c:245: warning: expecting prototype for mempool_init(). Prototype was for mempool_init_noprof() instead.
> mm/mempool.c:271: warning: expecting prototype for mempool_create_node(). Prototype was for mempool_create_node_noprof() instead.
Please stop. This is being fixed differently.
prev parent reply other threads:[~2024-03-29 3:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 3:01 Jiapeng Chong
2024-03-29 3:22 ` Matthew Wilcox [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=ZgY0CGZGgV7kgehP@casper.infradead.org \
--to=willy@infradead.org \
--cc=abaci@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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