From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andi Kleen <andi@firstfloor•org>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Naoya Horiguchi <n-horiguchi@ah•jp.nec.com>,
Wu Fengguang <fengguang.wu@intel•com>
Subject: linux-next: build warning after merge of the final tree (hwpoison tree related)
Date: Mon, 27 Sep 2010 15:28:04 +1000 [thread overview]
Message-ID: <20100927152804.57c2d66e.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 440 bytes --]
Hi Andi,
After merging the final tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:
mm/hugetlb.c:2950: warning: 'is_hugepage_on_freelist' defined but not used
Introduced by commit 19b31e29073e272e49a3d38972c132c49383d5d4 ("HWPOISON,
hugetlb: add free check to dequeue_hwpoison_huge_page()").
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2010-09-27 5:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 5:28 Stephen Rothwell [this message]
2010-09-27 6:56 ` linux-next: build warning after merge of the final tree (hwpoison tree related) Wu Fengguang
2010-09-27 7:02 ` Andi Kleen
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=20100927152804.57c2d66e.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=andi@firstfloor$(echo .)org \
--cc=fengguang.wu@intel$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=n-horiguchi@ah$(echo .)jp.nec.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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