All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, acme@redhat.com
Subject: Re: [PATCH -next] alpha: fix link error re stacktrace
Date: Mon, 9 Feb 2009 23:39:45 +0100	[thread overview]
Message-ID: <20090209223945.GA11841@elte.hu> (raw)
In-Reply-To: <20090209213836.GA9492@x200.localdomain>


* Alexey Dobriyan <adobriyan@gmail.com> wrote:

> 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

This didnt apply to the latest tracing tree due to other, interacting changes - i 
have applied the commit below - thanks Alexey!

	Ingo

----------------->
>From 510223da040cb7a7d6f524b12eeed03b3845aea1 Mon Sep 17 00:00:00 2001
From: Alexey Dobriyan <adobriyan@gmail.com>
Date: Tue, 10 Feb 2009 00:38:36 +0300
Subject: [PATCH] alpha: fix link error re stacktrace

Fix link error on alpha (which doesn't implenent stacktrace support).

Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
 kernel/trace/Kconfig |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
index 3a33128..79be773 100644
--- a/kernel/trace/Kconfig
+++ b/kernel/trace/Kconfig
@@ -310,7 +310,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

      parent reply	other threads:[~2009-02-09 22:39 UTC|newest]

Thread overview: 13+ 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 16:53   ` Randy Dunlap
2009-02-09 17:00   ` Steve Wise
2009-02-09 17:01     ` [ofa-general] " Randy Dunlap
2009-02-09 17:01       ` 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
2009-02-10 12:25     ` Ingo Molnar
2009-02-09 22:39   ` Ingo Molnar [this message]

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=20090209223945.GA11841@elte.hu \
    --to=mingo@elte.hu \
    --cc=acme@redhat.com \
    --cc=adobriyan@gmail.com \
    --cc=linux-next@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.