linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Xishi Qiu <qiuxishi@huawei.com>
To: Minchan Kim <minchan@kernel.org>,
	ngupta@vflare.org, sergey.senozhatsky.work@gmail.com,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Linux MM <linux-mm@kvack.org>, LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH V2] mm: fix typo of cache_alloc_zspage()
Date: Thu, 29 Dec 2016 15:54:23 +0800	[thread overview]
Message-ID: <5864C12F.60709@huawei.com> (raw)
In-Reply-To: <58646FB7.2040502@huawei.com>

Delete extra semicolon, it was introduced in
3783689 zsmalloc: introduce zspage structure

Signed-off-by: Xishi Qiu <qiuxishi@huawei.com>
---
 mm/zsmalloc.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/mm/zsmalloc.c b/mm/zsmalloc.c
index 9cc3c0b..2d6c92e 100644
--- a/mm/zsmalloc.c
+++ b/mm/zsmalloc.c
@@ -364,7 +364,7 @@ static struct zspage *cache_alloc_zspage(struct zs_pool *pool, gfp_t flags)
 {
 	return kmem_cache_alloc(pool->zspage_cachep,
 			flags & ~(__GFP_HIGHMEM|__GFP_MOVABLE));
-};
+}
 
 static void cache_free_zspage(struct zs_pool *pool, struct zspage *zspage)
 {
-- 
1.8.3.1


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

  parent reply	other threads:[~2016-12-29  7:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-29  2:06 mm: fix typo of cache_alloc_zspage() Xishi Qiu
2016-12-29  6:44 ` Minchan Kim
2016-12-29  6:52   ` Sergey Senozhatsky
2016-12-29  6:59     ` Minchan Kim
2016-12-29  7:34       ` Sergey Senozhatsky
2016-12-29  7:56         ` Minchan Kim
2016-12-29  8:03           ` Sergey Senozhatsky
2016-12-29 10:34           ` Xishi Qiu
2016-12-30  1:07             ` Sergey Senozhatsky
2016-12-29  7:54 ` Xishi Qiu [this message]
2017-01-06  4:08   ` [PATCH] mm: fix some typos in mm/zsmalloc.c Xishi Qiu
2017-01-06  4:38     ` Minchan Kim

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=5864C12F.60709@huawei.com \
    --to=qiuxishi@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --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).