From: Randy Dunlap <randy.dunlap@oracle.com>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for June 6 (frontswap)
Date: Wed, 8 Jun 2011 09:28:44 -0700 [thread overview]
Message-ID: <20110608092844.66352540.randy.dunlap@oracle.com> (raw)
In-Reply-To: <b06ff74d-fc79-4c01-b159-9d352ca1a0f5@default>
On Mon, 6 Jun 2011 13:23:09 -0700 (PDT) Dan Magenheimer wrote:
> Hi Randy --
>
> Indeed you are correct! Thanks for catching that!
>
Please fix the tree in linux-next so that this build error does not
continue.
>
> Thanks... for the memory!
> I really could use more / my throughput's on the floor
> The balloon is flat / my swap disk's fat / I've OOM's in store
> Overcommitted so much
> (with apologies to Bob Hope)
>
>
> > -----Original Message-----
> > From: Randy Dunlap
> > Sent: Monday, June 06, 2011 2:06 PM
> > To: Stephen Rothwell; Dan Magenheimer
> > Cc: linux-next@vger.kernel.org; LKML
> > Subject: Re: linux-next: Tree for June 6 (frontswap)
> >
> > On Mon, 6 Jun 2011 13:20:36 +1000 Stephen Rothwell wrote:
> >
> > > Hi all,
> > >
> > > Changes since 20110603:
> >
> >
> > Does frontswap need to depend on SWAP?
> >
> > When SWAP is not enabled:
> >
> > mm/built-in.o: In function `frontswap_curr_pages':
> > (.text+0x467c1): undefined reference to `swap_lock'
> > mm/built-in.o: In function `frontswap_curr_pages':
> > (.text+0x467ce): undefined reference to `swap_list'
> > mm/built-in.o: In function `frontswap_curr_pages':
> > (.text+0x467e6): undefined reference to `swap_info'
> > mm/built-in.o: In function `frontswap_curr_pages':
> > (.text+0x467fe): undefined reference to `swap_lock'
> > mm/built-in.o: In function `frontswap_shrink':
> > (.text+0x4688d): undefined reference to `swap_lock'
> > mm/built-in.o: In function `frontswap_shrink':
> > (.text+0x46898): undefined reference to `swap_list'
> > mm/built-in.o: In function `frontswap_shrink':
> > (.text+0x468b6): undefined reference to `swap_info'
> > mm/built-in.o: In function `frontswap_shrink':
> > (.text+0x4690d): undefined reference to `swap_info'
> > mm/built-in.o: In function `frontswap_shrink':
> > (.text+0x469d3): undefined reference to `swap_lock'
> > mm/built-in.o: In function `frontswap_shrink':
> > (.text+0x469ec): undefined reference to `try_to_unuse'
> > mm/built-in.o: In function `frontswap_shrink':
> > (.text+0x46a1c): undefined reference to `swap_lock'
> > mm/built-in.o: In function `__frontswap_flush_area':
> > (.text+0x46aa4): undefined reference to `swap_info'
> > mm/built-in.o: In function `__frontswap_get_page':
> > (.text+0x46b1f): undefined reference to `swap_info'
> > mm/built-in.o: In function `__frontswap_put_page':
> > (.text+0x46bf8): undefined reference to `swap_info'
> > mm/built-in.o: In function `__frontswap_flush_page':
> > (.text+0x46d86): undefined reference to `swap_info'
> > mm/built-in.o: In function `frontswap_curr_pages':
> > (.text+0x467c1): undefined reference to `swap_lock'
> > mm/built-in.o: In function `frontswap_curr_pages':
> > (.text+0x467ce): undefined reference to `swap_list'
> > mm/built-in.o: In function `frontswap_curr_pages':
> > (.text+0x467e6): undefined reference to `swap_info'
> > mm/built-in.o: In function `frontswap_curr_pages':
> > (.text+0x467fe): undefined reference to `swap_lock'
> > mm/built-in.o: In function `frontswap_shrink':
> > (.text+0x4688d): undefined reference to `swap_lock'
> > mm/built-in.o: In function `frontswap_shrink':
> > (.text+0x46898): undefined reference to `swap_list'
> > mm/built-in.o: In function `frontswap_shrink':
> > (.text+0x468b6): undefined reference to `swap_info'
> > mm/built-in.o: In function `frontswap_shrink':
> > (.text+0x4690d): undefined reference to `swap_info'
> > mm/built-in.o: In function `frontswap_shrink':
> > (.text+0x469d3): undefined reference to `swap_lock'
> > mm/built-in.o: In function `frontswap_shrink':
> > (.text+0x469ec): undefined reference to `try_to_unuse'
> > mm/built-in.o: In function `frontswap_shrink':
> > (.text+0x46a1c): undefined reference to `swap_lock'
> > mm/built-in.o: In function `__frontswap_flush_area':
> > (.text+0x46aa4): undefined reference to `swap_info'
> > mm/built-in.o: In function `__frontswap_get_page':
> > (.text+0x46b1f): undefined reference to `swap_info'
> > mm/built-in.o: In function `__frontswap_put_page':
> > (.text+0x46bf8): undefined reference to `swap_info'
> > mm/built-in.o: In function `__frontswap_flush_page':
> > (.text+0x46d86): undefined reference to `swap_info'
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-06-08 16:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 3:20 linux-next: Tree for June 6 Stephen Rothwell
2011-06-06 19:55 ` linux-next: Tree for June 6 (sctp) Randy Dunlap
2011-06-06 20:06 ` David Miller
2011-06-06 20:06 ` linux-next: Tree for June 6 (frontswap) Randy Dunlap
2011-06-06 20:23 ` Dan Magenheimer
2011-06-08 16:28 ` Randy Dunlap [this message]
2011-06-08 17:01 ` Dan Magenheimer
2011-06-09 0:12 ` Dan Magenheimer
2011-06-09 1:04 ` Stephen Rothwell
2011-06-07 9:48 ` linux-next: Tree for June 6 Catalin Marinas
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=20110608092844.66352540.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=dan.magenheimer@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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