From: Alexey Dobriyan <adobriyan@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
"David S. Miller" <davem@davemloft.net>
Cc: linux-next@vger.kernel.org, Ken Chen <kenchen@google.com>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: linux-next: proc tree build failure
Date: Fri, 28 Nov 2008 11:05:55 +0300 [thread overview]
Message-ID: <20081128080555.GC3495@x200.localdomain> (raw)
In-Reply-To: <20081124181559.3896a756.sfr@canb.auug.org.au>
On Mon, Nov 24, 2008 at 06:15:59PM +1100, Stephen Rothwell wrote:
> Today's linux-next build (sparc64 allmodconfig) failed like this:
>
> fs/proc/base.c:362: undefined reference to `save_stack_trace_tsk'
>
> It has been failing like this for some time.
>
> Caused by commit 788ff43b53179f3af8677d59c87104aff1f75bde ("proc:
> add /proc/*/stack") which has been fixed up for MIPS, but needs another
> fix for Sparc.
David, can you implement save_stack_trace_tsk() for sparc64? I have no idea
how to do it or is it doable at all.
next prev parent reply other threads:[~2008-11-28 8:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 7:15 linux-next: proc tree build failure Stephen Rothwell
2008-11-28 8:05 ` Alexey Dobriyan [this message]
2008-11-28 9:00 ` David Miller
2008-11-28 10:25 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2009-03-30 6:43 Stephen Rothwell
2009-01-23 6:15 Stephen Rothwell
2009-01-23 7:09 ` Cyrill Gorcunov
2009-01-23 18:48 ` Alexey Dobriyan
2009-01-23 19:26 ` Cyrill Gorcunov
2009-01-23 19:41 ` Cyrill Gorcunov
2009-01-23 20:26 ` Cyrill Gorcunov
2008-11-20 6:24 Stephen Rothwell
2008-11-20 8:43 ` Eric W. Biederman
2008-11-10 5:29 Stephen Rothwell
2008-11-10 5:53 ` Alexey Dobriyan
2008-11-10 7:36 ` Ingo Molnar
2008-10-21 7:21 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=20081128080555.GC3495@x200.localdomain \
--to=adobriyan@gmail.com \
--cc=davem@davemloft.net \
--cc=kenchen@google.com \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--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