All of lore.kernel.org
 help / color / mirror / Atom feed
From: BaoJun Luo <baojun.luo@samsung.com>
To: rjw@rjwysocki.net, pavel@ucw.cz
Cc: linux-pm@vger.kernel.org
Subject: [PATCH] PM/hibernate: Delete the redundant parameters of the swsusp_alloc()
Date: Tue, 23 May 2017 09:47:13 +0800	[thread overview]
Message-ID: <14144.1925465644$1505300903@news.gmane.org> (raw)
In-Reply-To: CGME20170523014807epcas1p44d542b7f3bb7ed19f05a11b874231c55@epcas1p4.samsung.com

>From 2a91f46951c676a96621ab7505e168a2dc619064 Mon Sep 17 00:00:00 2001
From: "baojun.luo" <baojun.luo@samsung.com>
Date: Mon, 22 May 2017 15:30:19 +0800
Subject: [PATCH] PM/hibernate: Delete the redundant parameters of the
 swsusp_alloc()

The first parameter of swsusp_alloc has not been used. The patch to make
sure to delete the redundant parameters

Signed-off-by: baojun.luo <baojun.luo@samsung.com>
---
 kernel/power/snapshot.c | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/kernel/power/snapshot.c b/kernel/power/snapshot.c
index 3b1e0f3..0f8a039 100644
--- a/kernel/power/snapshot.c
+++ b/kernel/power/snapshot.c
@@ -1929,8 +1929,7 @@ static inline unsigned int alloc_highmem_pages(struct memory_bitmap *bm,
  * also be located in the high memory, because of the way in which
  * copy_data_pages() works.
  */
-static int swsusp_alloc(struct memory_bitmap *orig_bm,
-			struct memory_bitmap *copy_bm,
+static int swsusp_alloc(struct memory_bitmap *copy_bm,
 			unsigned int nr_pages, unsigned int nr_highmem)
 {
 	if (nr_highmem > 0) {
@@ -1976,7 +1975,7 @@ asmlinkage __visible int swsusp_save(void)
 		return -ENOMEM;
 	}
 
-	if (swsusp_alloc(&orig_bm, &copy_bm, nr_pages, nr_highmem)) {
+	if (swsusp_alloc(&copy_bm, nr_pages, nr_highmem)) {
 		printk(KERN_ERR "PM: Memory allocation failed\n");
 		return -ENOMEM;
 	}
-- 
1.9.1

           reply	other threads:[~2017-05-23  1:48 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CGME20170523014807epcas1p44d542b7f3bb7ed19f05a11b874231c55@epcas1p4.samsung.com>]

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='14144.1925465644$1505300903@news.gmane.org' \
    --to=baojun.luo@samsung.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@rjwysocki.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.