public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Greg KH <greg@kroah.com>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (staging tree related)
Date: Wed, 6 Mar 2013 17:23:38 -0500	[thread overview]
Message-ID: <20130306222338.GC11269@phenom.dumpdata.com> (raw)
In-Reply-To: <20130307075055.a8722b275ed6edb53839e13b@canb.auug.org.au>

On Thu, Mar 07, 2013 at 07:50:55AM +1100, Stephen Rothwell wrote:
> Hi Konrad,
> 
> On Wed, 6 Mar 2013 15:04:44 -0500 Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> >
> > So, irrespective of zcache, I also see this:
> > 
> > init/built-in.o: In function `.rd_load_image':
> > (.init.text+0x1b24): undefined reference to `.__bswapdi2'
> > arch/powerpc/kernel/built-in.o: In function `.iowa_writeq':
> > io-workarounds.c:(.text+0x2f778): undefined reference to `.__bswapdi2'
> > arch/powerpc/kernel/built-in.o: In function `.iowa_readq':
> > io-workarounds.c:(.text+0x2f848): undefined reference to `.__bswapdi2'
> > arch/powerpc/platforms/built-in.o: In function `.spiderpci_readq':
> > spider-pci.c:(.text+0x2a84c): undefined reference to `.__bswapdi2'
> > arch/powerpc/platforms/built-in.o: In function `.scc_pciex_readq':
> > celleb_scc_pciex.c:(.text+0x2fc4c): undefined reference to `.__bswapdi2'
> > fs/built-in.o:(.text+0x9717c): more undefined references to `.__bswapdi2' follow
> > 
> > Is that new?
> 
> I don't get those.  What compiler version and config are you using?

powerpc64-unknown-linux-gnu-gcc (GCC) 4.4.2

The defconfig with CONFIG_STAGING=y, CONFIG_CONFIGFS_FS=y, CONFIG_FRONTSWAP=y and CONFIG_ZCACHE_* =y


  reply	other threads:[~2013-03-06 22:23 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06  0:35 linux-next: build failure after merge of the final tree (staging tree related) Stephen Rothwell
2013-03-06  0:43 ` Greg KH
2013-03-06 13:56   ` Konrad Rzeszutek Wilk
2013-03-06 20:04     ` Konrad Rzeszutek Wilk
2013-03-06 20:46       ` Stephen Rothwell
2013-03-06 20:50       ` Stephen Rothwell
2013-03-06 22:23         ` Konrad Rzeszutek Wilk [this message]
2013-03-06 22:11       ` Greg KH
2013-03-06 22:21         ` Konrad Rzeszutek Wilk
  -- strict thread matches above, loose matches on Subject: below --
2014-02-10  4:54 Stephen Rothwell
2014-02-10  5:04 ` Greg KH
2013-06-19  8:10 Stephen Rothwell
2013-06-19  9:26 ` Peng Tao
2013-06-19 14:37   ` Greg KH
2013-06-20 10:52     ` Peng Tao
2013-06-24 22:40   ` Greg KH
2013-06-24 23:40     ` Stephen Rothwell
2013-06-24 23:50       ` Greg KH
2013-06-25  0:22         ` Peng Tao
2013-06-25  2:13           ` Greg KH
2013-04-24  7:56 linux-next: build failure after merge of the final tree (staging tree related)) Stephen Rothwell
2013-04-24 17:53 ` H Hartley Sweeten
2013-04-24 18:33 ` H Hartley Sweeten
2013-03-13  5:39 linux-next: build failure after merge of the final tree (staging tree related) Stephen Rothwell
2013-03-14 20:23 ` Paul Zimmerman
2013-03-14 20:33   ` Greg KH
2012-11-13  5:51 Stephen Rothwell
2012-11-13  9:24 ` Jonathan Cameron
2012-11-13 18:48 ` Greg KH
2012-09-24 14:29 Stephen Rothwell
2012-09-10  7:04 Stephen Rothwell
2012-09-10 17:31 ` Greg KH
2012-09-05  5:48 Stephen Rothwell
2012-09-06 18:06 ` Geert Uytterhoeven
2012-05-16 10:06 Stephen Rothwell
2012-05-16 12:49 ` Greg KH
2012-05-16 14:17   ` Dan Magenheimer
2012-05-16 15:10     ` Greg KH
2012-02-27  7:13 Stephen Rothwell
2012-02-27 21:16 ` Greg KH
2012-02-29  7:35   ` Chris Kelly
2012-02-29  7:52     ` Stephen Rothwell
2012-02-29 17:08       ` Chris Kelly
2012-02-13  6:19 Stephen Rothwell
2012-02-13  6:45 ` Greg KH
2012-02-13 14:13   ` Seth Jennings
2012-02-13 14:48   ` Seth Jennings
2012-02-13 15:03     ` Greg KH
2011-10-04  8:05 Stephen Rothwell
2011-10-04  8:49 ` Jonathan Cameron
2011-08-25  6:17 Stephen Rothwell
2011-08-24  5:47 Stephen Rothwell
2011-08-24 21:16 ` Greg KH
2011-08-24 22:54   ` Stephen Rothwell
2011-08-24 22:57     ` Greg KH
2011-08-24 23:28       ` Stephen Rothwell
2011-07-18  9:36 Stephen Rothwell
2011-07-19  1:01 ` Greg KH
2011-07-28  3:35   ` Stephen Rothwell
2011-08-02 23:17     ` Greg KH
2011-07-07  6:25 Stephen Rothwell
2011-07-07 13:44 ` Greg KH

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=20130306222338.GC11269@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=greg@kroah.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