From: Michael Neuling <mikey@neuling.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (powerpc tree related)
Date: Fri, 11 Jan 2013 17:04:06 +1100 [thread overview]
Message-ID: <28677.1357884246@ale.ozlabs.ibm.com> (raw)
In-Reply-To: <20130111165241.44a5ede6b24c997810be74e1@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> arch/powerpc/kernel/kgdb.c: In function 'kgdb_arch_exit':
> arch/powerpc/kernel/kgdb.c:492:2: error: '__debugger_breakx_match' undeclared (first use in this function)
>
> Caused by commit 9422de3e953d ("powerpc: Hardware breakpoints rewrite to
> handle non DABR breakpoint registers"). I applied "powerpc: Fix typo in
> breakpoint kgdb code" from Mikey for this.
>
> arch/powerpc/kernel/exceptions-64s.S: Assembler messages:
> arch/powerpc/kernel/exceptions-64s.S:1204: Error: attempt to move .org backwards
>
> Not sure what caused that - probably a combination of patches adding code
> low down. I have just left this broken for today.
FWIW I posted this earlier
http://patchwork.ozlabs.org/patch/211184/
Mikey
next prev parent reply other threads:[~2013-01-11 6:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 5:52 linux-next: build failure after merge of the final tree (powerpc tree related) Stephen Rothwell
2013-01-11 6:04 ` Michael Neuling [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-12-09 6:32 Stephen Rothwell
2012-09-06 7:11 Stephen Rothwell
2012-09-06 8:20 ` Ananth N Mavinakayanahalli
2011-06-30 6:36 Stephen Rothwell
2011-06-30 7:09 ` Benjamin Herrenschmidt
2011-05-05 3:41 Stephen Rothwell
2011-03-14 9:38 Stephen Rothwell
2011-03-14 20:37 ` Benjamin Herrenschmidt
2011-03-14 20:51 ` David Miller
2011-03-14 21:17 ` Thomas Gleixner
2011-03-14 21:21 ` Lennert Buytenhek
2010-12-03 5:32 Stephen Rothwell
2010-12-03 5:59 ` Benjamin Herrenschmidt
2010-12-03 6:08 ` Stephen Rothwell
2010-12-03 11:26 ` Josh Boyer
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=28677.1357884246@ale.ozlabs.ibm.com \
--to=mikey@neuling.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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).