linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Greg KH <greg@kroah.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	ppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: linux-next: build failure after merge of the final tree (tty tree related)
Date: Thu, 25 Aug 2011 10:22:05 -0500	[thread overview]
Message-ID: <4E56689D.3080202@freescale.com> (raw)
In-Reply-To: <20110825140820.GA9126@kroah.com>

Greg KH wrote:
>> > MSR_GS is defined in arch/powerpc/include/asm/reg_booke.h which is
>> > included by arch/powerpc/include/asm/reg.h but only when defined
>> > (CONFIG_BOOKE) || defined(CONFIG_40x).
> Thanks for the report.
> 
> Timur, care to send a fixup patch for this so this gets resolved?

Is there some trick to building allyesconfig on PowerPC?  When I do try that, I
get all sorts of weird build errors, and it dies long before it gets to my
driver.  I get stuff like:

  LD      arch/powerpc/sysdev/xics/built-in.o
WARNING: arch/powerpc/sysdev/xics/built-in.o(.text+0x1310): Section mismatch in
reference from the function .icp_native_init() to the function
.init.text:.icp_native_init_one_node()
The function .icp_native_init() references
the function __init .icp_native_init_one_node().
This is often because .icp_native_init lacks a __init
annotation or the annotation of .icp_native_init_one_node is wrong.

and

  AS      arch/powerpc/kernel/head_64.o
arch/powerpc/kernel/exceptions-64s.S: Assembler messages:
arch/powerpc/kernel/exceptions-64s.S:1151: Error: attempt to move .org backwards
arch/powerpc/kernel/exceptions-64s.S:1160: Error: attempt to move .org backwards
make[1]: *** [arch/powerpc/kernel/head_64.o] Error 1

I guess I don't have the right compiler.

Anyway, I think I know how to fix the break that Stephen is seeing.  I will post
a v4 patch in a few minutes.


-- 
Timur Tabi
Linux kernel developer at Freescale

  parent reply	other threads:[~2011-08-25 15:22 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-25  6:18 linux-next: build failure after merge of the final tree (tty tree related) Stephen Rothwell
2011-08-25 14:08 ` Greg KH
2011-08-25 14:28   ` Timur Tabi
2011-08-25 15:22   ` Timur Tabi [this message]
2011-08-25 15:51     ` Stephen Rothwell
2011-08-25 16:09       ` Arnaud Lacombe
2011-08-26  0:39         ` Stephen Rothwell
2011-08-26 15:47           ` Arnaud Lacombe
2011-09-11  4:23             ` Stephen Rothwell
2011-09-11  9:05               ` Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
2013-10-28 14:33 Stephen Rothwell
2013-10-28 14:49 ` Michal Simek
2013-10-28 16:05 ` Sören Brinkmann
2013-10-28 16:33   ` Greg KH
2013-10-29  7:04     ` Stephen Rothwell
2013-09-27  8:21 Stephen Rothwell
2013-09-28  1:04 ` Greg KH
2013-04-02  7:57 Stephen Rothwell
2012-11-26 13:49 Stephen Rothwell
2012-11-26 14:35 ` Steven Rostedt
2012-11-26 23:05   ` Stephen Rothwell
2012-12-13 23:32     ` Stephen Rothwell
2012-12-13 23:38       ` Greg KH
2012-12-14  0:11         ` Steven Rostedt
2012-09-24 14:36 Stephen Rothwell
2012-09-25 22:41 ` Greg KH
2012-07-20  5:02 Stephen Rothwell
2012-07-25 22:47 ` Greg KH
2012-07-26  0:23   ` Alan Cox
2012-07-25 22:52 ` Stephen Rothwell
2010-12-17  6:11 Stephen Rothwell
2010-12-17  7:04 ` Greg KH
2010-12-17 10:16   ` Thomas Gleixner
2011-01-06  3:27     ` Stephen Rothwell
2011-01-06 18:45       ` Greg KH
2010-11-12  1:57 Stephen Rothwell
2010-11-12 10:44 ` Alan Cox

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=4E56689D.3080202@freescale.com \
    --to=timur@freescale.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).