All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Liu <lliubbo@gmail.com>
To: akpm@linux-foundation.org
Cc: fengguang.wu@intel.com, yuanhan.liu@linux.intel.com,
	sfr@canb.auug.org.au, linux-next@vger.kernel.org,
	linux-mm@kvack.org, Bob Liu <lliubbo@gmail.com>
Subject: [PATCH] mm: rmap: fix build warning
Date: Thu, 25 Oct 2012 16:50:50 +0800	[thread overview]
Message-ID: <1351155050-4055-1-git-send-email-lliubbo@gmail.com> (raw)

mm/rmap.c: In function 'try_to_unmap_cluster':
mm/rmap.c:1361:9: warning: unused variable 'pud' [-Wunused-variable]
mm/rmap.c:1360:9: warning: unused variable 'pgd' [-Wunused-variable]

I forgot to del these variable in my commit:
0981230ec3206f98dcc58febfef9fd35b540d25a mm: introduce mm_find_pmd()

Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Reported-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Signed-off-by: Bob Liu <lliubbo@gmail.com>
---
 mm/rmap.c |    2 --
 1 file changed, 2 deletions(-)

diff --git a/mm/rmap.c b/mm/rmap.c
index 6c686c2..98b100e 100644
--- a/mm/rmap.c
+++ b/mm/rmap.c
@@ -1360,8 +1360,6 @@ static int try_to_unmap_cluster(unsigned long cursor, unsigned int *mapcount,
 		struct vm_area_struct *vma, struct page *check_page)
 {
 	struct mm_struct *mm = vma->vm_mm;
-	pgd_t *pgd;
-	pud_t *pud;
 	pmd_t *pmd;
 	pte_t *pte;
 	pte_t pteval;
-- 
1.7.9.5

WARNING: multiple messages have this Message-ID (diff)
From: Bob Liu <lliubbo@gmail.com>
To: akpm@linux-foundation.org
Cc: fengguang.wu@intel.com, yuanhan.liu@linux.intel.com,
	sfr@canb.auug.org.au, linux-next@vger.kernel.org,
	linux-mm@kvack.org, Bob Liu <lliubbo@gmail.com>
Subject: [PATCH] mm: rmap: fix build warning
Date: Thu, 25 Oct 2012 16:50:50 +0800	[thread overview]
Message-ID: <1351155050-4055-1-git-send-email-lliubbo@gmail.com> (raw)

mm/rmap.c: In function 'try_to_unmap_cluster':
mm/rmap.c:1361:9: warning: unused variable 'pud' [-Wunused-variable]
mm/rmap.c:1360:9: warning: unused variable 'pgd' [-Wunused-variable]

I forgot to del these variable in my commit:
0981230ec3206f98dcc58febfef9fd35b540d25a mm: introduce mm_find_pmd()

Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Reported-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Signed-off-by: Bob Liu <lliubbo@gmail.com>
---
 mm/rmap.c |    2 --
 1 file changed, 2 deletions(-)

diff --git a/mm/rmap.c b/mm/rmap.c
index 6c686c2..98b100e 100644
--- a/mm/rmap.c
+++ b/mm/rmap.c
@@ -1360,8 +1360,6 @@ static int try_to_unmap_cluster(unsigned long cursor, unsigned int *mapcount,
 		struct vm_area_struct *vma, struct page *check_page)
 {
 	struct mm_struct *mm = vma->vm_mm;
-	pgd_t *pgd;
-	pud_t *pud;
 	pmd_t *pmd;
 	pte_t *pte;
 	pte_t pteval;
-- 
1.7.9.5


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

             reply	other threads:[~2012-10-25  8:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-25  8:50 Bob Liu [this message]
2012-10-25  8:50 ` [PATCH] mm: rmap: fix build warning Bob Liu

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=1351155050-4055-1-git-send-email-lliubbo@gmail.com \
    --to=lliubbo@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=fengguang.wu@intel.com \
    --cc=linux-mm@kvack.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=yuanhan.liu@linux.intel.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 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.