From: Pekka Enberg <penberg@cs•helsinki.fi>
To: Ingo Molnar <mingo@elte•hu>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Thomas Gleixner <tglx@linutronix•de>,
"H. Peter Anvin" <hpa@zytor•com>,
Peter Zijlstra <peterz@infradead•org>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Thiago Farina <tfransosi@gmail•com>
Subject: Re: linux-next: tip tree build failure
Date: Tue, 5 Jan 2010 09:39:40 +0200 [thread overview]
Message-ID: <84144f021001042339r29f151feja00d7af12a82c9a2@mail.gmail.com> (raw)
In-Reply-To: <20100104163159.GD23652@elte.hu>
On Mon, Jan 4, 2010 at 6:32 PM, Ingo Molnar <mingo@elte•hu> wrote:
>
> * Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
>> Hi all,
>>
>> Today's linux-next build (s390x defconfig) failed like this:
>>
>> kernel/panic.c:134: error: 'CALLER_ADDR0' undeclared (first use in this function)
>>
>> Caused by commit eba3fe4416f3cc2ce043fb304b6c35a69dca3bdb ("kernel: Use
>> CALLER_ADDR0 macro").
>
> Thanks - apparently CALLER_ADDR0 isnt generally available. I've reverted this
> patch for now.
Btw, we have _RET_IP_ which is pretty much the same thing and it is
available everywhere (SLUB uses it).
next prev parent reply other threads:[~2010-01-05 7:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-04 12:59 linux-next: tip tree build failure Stephen Rothwell
2010-01-04 16:32 ` Ingo Molnar
2010-01-05 3:39 ` Stephen Rothwell
2010-01-05 7:39 ` Pekka Enberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-11-11 9:13 Stephen Rothwell
2009-11-11 15:03 ` FUJITA Tomonori
2009-11-11 21:39 ` Stephen Rothwell
2009-08-24 6:54 Stephen Rothwell
2009-08-24 6:58 ` Peter Zijlstra
2009-08-24 7:32 ` Ingo Molnar
2009-06-12 6:30 Stephen Rothwell
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=84144f021001042339r29f151feja00d7af12a82c9a2@mail.gmail.com \
--to=penberg@cs$(echo .)helsinki.fi \
--cc=hpa@zytor$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=peterz@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tfransosi@gmail$(echo .)com \
--cc=tglx@linutronix$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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