From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Wanpeng Li <liwanp@linux.vnet.ibm.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
Seth Jennings <sjenning@linux.vnet.ibm.com>,
Konrad Rzeszutek Wilk <konrad@darnok.org>,
Minchan Kim <minchan@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Bob Liu <bob.liu@oracle.com>
Subject: Re: [PATCH PART3 v3 2/6] staging: ramster: Move debugfs code out of ramster.c file
Date: Fri, 12 Apr 2013 20:07:03 -0700 [thread overview]
Message-ID: <20130413030703.GA22129@kroah.com> (raw)
In-Reply-To: <1365813371-19006-2-git-send-email-liwanp@linux.vnet.ibm.com>
On Sat, Apr 13, 2013 at 08:36:06AM +0800, Wanpeng Li wrote:
> Note that at this point there is no CONFIG_RAMSTER_DEBUG
> option in the Kconfig. So in effect all of the counters
> are nop until that option gets introduced in patch:
> ramster/debug: Add CONFIG_RAMSTER_DEBUG Kconfig entry
This patch breaks the build again, so of course, I can't take it:
drivers/built-in.o: In function `ramster_flnode_alloc.isra.5':
ramster.c:(.text+0x1b6a6e): undefined reference to `ramster_flnodes_max'
ramster.c:(.text+0x1b6a7e): undefined reference to `ramster_flnodes_max'
drivers/built-in.o: In function `ramster_count_foreign_pages':
(.text+0x1b7205): undefined reference to `ramster_foreign_pers_pages_max'
drivers/built-in.o: In function `ramster_count_foreign_pages':
(.text+0x1b7215): undefined reference to `ramster_foreign_pers_pages_max'
drivers/built-in.o: In function `ramster_count_foreign_pages':
(.text+0x1b7235): undefined reference to `ramster_foreign_eph_pages_max'
drivers/built-in.o: In function `ramster_count_foreign_pages':
(.text+0x1b7249): undefined reference to `ramster_foreign_eph_pages_max'
drivers/built-in.o: In function `ramster_debugfs_init':
(.init.text+0xd620): undefined reference to `ramster_foreign_eph_pages_max'
drivers/built-in.o: In function `ramster_debugfs_init':
(.init.text+0xd656): undefined reference to `ramster_foreign_pers_pages_max'
I thought you fixed this :(
--
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:[~2013-04-13 3:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 0:36 [PATCH PART3 v3 0/6] staging: zcache/ramster: fix and ramster/debugfs improvement Wanpeng Li
2013-04-13 0:36 ` [PATCH PART3 v3 2/6] staging: ramster: Move debugfs code out of ramster.c file Wanpeng Li
2013-04-13 3:07 ` Greg Kroah-Hartman [this message]
2013-04-13 12:52 ` Wanpeng Li
2013-04-13 12:52 ` Wanpeng Li
2013-04-13 0:36 ` [PATCH PART3 v3 3/6] staging: ramster/debug: Use an array to initialize/use debugfs attributes Wanpeng Li
2013-04-13 0:36 ` [PATCH PART3 v3 4/6] staging: ramster: Add incremental accessory counters Wanpeng Li
2013-04-13 0:36 ` [PATCH PART3 v3 5/6] staging: ramster/debug: Add CONFIG_RAMSTER_DEBUG Kconfig entry Wanpeng Li
2013-04-13 0:36 ` [PATCH PART3 v3 6/6] staging: zcache/debug: fix coding style Wanpeng Li
2013-04-13 0:36 ` [PATCH PART2 v2 7/7] staging: ramster: add how-to for ramster Wanpeng Li
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=20130413030703.GA22129@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=bob.liu@oracle.com \
--cc=dan.magenheimer@oracle.com \
--cc=konrad@darnok.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liwanp@linux.vnet.ibm.com \
--cc=minchan@kernel.org \
--cc=sjenning@linux.vnet.ibm.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