From: Randy Dunlap <rdunlap@infradead.org>
To: Souptick Joarder <jrdr.linux@gmail.com>,
minchan@kernel.org, ngupta@vflare.org,
sergey.senozhatsky.work@gmail.com
Cc: linux-mm@kvack.org
Subject: Re: [PATCH] mm: zsmalloc: Replace return type int with bool
Date: Mon, 19 Feb 2018 11:43:42 -0800 [thread overview]
Message-ID: <a13bc194-4fad-e8b2-1f75-9ab851ffcfc3@infradead.org> (raw)
In-Reply-To: <20180219194216.GA26165@jordon-HP-15-Notebook-PC>
On 02/19/18 11:42, Souptick Joarder wrote:
> zs_register_migration() returns either 0 or 1.
> So the return type int should be replaced with bool.
>
> Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
> ---
> mm/zsmalloc.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/mm/zsmalloc.c b/mm/zsmalloc.c
> index c301350..e238354 100644
> --- a/mm/zsmalloc.c
> +++ b/mm/zsmalloc.c
> @@ -295,7 +295,7 @@ struct mapping_area {
> };
>
> #ifdef CONFIG_COMPACTION
> -static int zs_register_migration(struct zs_pool *pool);
> +static bool zs_register_migration(struct zs_pool *pool);
> static void zs_unregister_migration(struct zs_pool *pool);
> static void migrate_lock_init(struct zspage *zspage);
> static void migrate_read_lock(struct zspage *zspage);
> @@ -306,7 +306,7 @@ struct mapping_area {
> #else
> static int zsmalloc_mount(void) { return 0; }
> static void zsmalloc_unmount(void) {}
> -static int zs_register_migration(struct zs_pool *pool) { return 0; }
> +static bool zs_register_migration(struct zs_pool *pool) { return 0; }
return false;
> static void zs_unregister_migration(struct zs_pool *pool) {}
> static void migrate_lock_init(struct zspage *zspage) {}
> static void migrate_read_lock(struct zspage *zspage) {}
> @@ -2101,17 +2101,17 @@ void zs_page_putback(struct page *page)
> .putback_page = zs_page_putback,
> };
>
> -static int zs_register_migration(struct zs_pool *pool)
> +static bool zs_register_migration(struct zs_pool *pool)
> {
> pool->inode = alloc_anon_inode(zsmalloc_mnt->mnt_sb);
> if (IS_ERR(pool->inode)) {
> pool->inode = NULL;
> - return 1;
> + return true;
> }
>
> pool->inode->i_mapping->private_data = pool;
> pool->inode->i_mapping->a_ops = &zsmalloc_aops;
> - return 0;
> + return false;
> }
>
> static void zs_unregister_migration(struct zs_pool *pool)
> --
thanks,
--
~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>
next prev parent reply other threads:[~2018-02-19 19:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 19:42 [PATCH] mm: zsmalloc: Replace return type int with bool Souptick Joarder
2018-02-19 19:43 ` Randy Dunlap [this message]
2018-02-20 3:37 ` kbuild test robot
2018-02-20 7:39 ` Souptick Joarder
2018-02-20 9:08 ` Minchan Kim
2018-02-20 10:55 ` Souptick Joarder
2018-02-20 12:52 ` Matthew Wilcox
2018-02-20 13:37 ` Matthew Wilcox
2018-02-20 15:18 ` Souptick Joarder
2018-02-20 3:37 ` [PATCH] mm: zsmalloc: fix boolreturn.cocci warnings kbuild test robot
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=a13bc194-4fad-e8b2-1f75-9ab851ffcfc3@infradead.org \
--to=rdunlap@infradead.org \
--cc=jrdr.linux@gmail.com \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=sergey.senozhatsky.work@gmail.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;
as well as URLs for NNTP newsgroup(s).