From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: "Stephen Rothwell" <sfr@canb.auug.org.au>,
"Ingo Molnar" <mingo@elte.hu>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
linux-next@vger.kernel.org
Subject: Re: [PATCH -next] alpha: fix link error re stacktrace
Date: Mon, 9 Feb 2009 19:55:01 -0200 [thread overview]
Message-ID: <20090209215501.GB12820@ghostprotocols.net> (raw)
In-Reply-To: <20090209213836.GA9492@x200.localdomain>
Em Tue, Feb 10, 2009 at 12:38:36AM +0300, Alexey Dobriyan escreveu:
> Please, fold this into 32c0bd9624115041cfec31c0436995418083090a
> "blktrace: the ftrace interface needs CONFIG_TRACING"
> to fix link error on alpha (which doesn't implenent stacktrace support)
>
> --- a/block/Kconfig
> +++ b/block/Kconfig
> @@ -51,7 +51,7 @@ config BLK_DEV_IO_TRACE
> select DEBUG_FS
> select TRACEPOINTS
> select TRACING
> - select STACKTRACE
> + select STACKTRACE if STACKTRACE_SUPPORT
> help
> Say Y here if you want to be able to trace the block layer actions
> on a given queue. Tracing allows you to see any traffic happening
Well, with 51a763dd84253bab1d0a1e68e11a7753d1b702ca this can as well be
reverted :-)
- Arnaldo
next prev parent reply other threads:[~2009-02-09 21:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 8:39 linux-next: Tree for February 9 Stephen Rothwell
2009-02-09 16:53 ` [ofa-general] Re: linux-next: Tree for February 9 (infiniband) Randy Dunlap
2009-02-09 17:00 ` Steve Wise
2009-02-09 17:01 ` [ofa-general] " Randy Dunlap
2009-02-09 17:15 ` linux-next: Tree for February 9 (ide-dma) Randy Dunlap
2009-02-09 18:56 ` Bartlomiej Zolnierkiewicz
2009-02-09 21:50 ` Randy Dunlap
2009-02-09 21:38 ` [PATCH -next] alpha: fix link error re stacktrace Alexey Dobriyan
2009-02-09 21:55 ` Arnaldo Carvalho de Melo [this message]
2009-02-10 12:25 ` Ingo Molnar
2009-02-09 22:39 ` Ingo Molnar
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=20090209215501.GB12820@ghostprotocols.net \
--to=acme@redhat.com \
--cc=adobriyan@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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).