public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: David Daney <david.daney@cavium.com>
Cc: linux-mips@linux-mips.org, linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: [PATCH 2/2] perf tools: Hook up MIPS unwind and dwarf-regs in the Makefile
Date: Wed, 8 Apr 2015 11:58:53 +0200	[thread overview]
Message-ID: <20150408095853.GC14284@krava.redhat.com> (raw)
In-Reply-To: <f43306ea57733a711b66a92a5e5f17fd1a6f3f8a.1428450297.git.ralf@linux-mips.org>

On Wed, Apr 08, 2015 at 01:58:47AM +0200, David Daney wrote:
> From: David Daney <david.daney@cavium.com>
> 
> Define a new symbol (ARCH_SUPPORTS_LIBUNWIND) in config/Makefile.
> Use this from x86 and MIPS to gate testing of libunwind.

hum.. hows ARCH_SUPPORTS_LIBUNWIND being used?
I dont see it.. are there more patches? ;-)

jirka

  reply	other threads:[~2015-04-08  9:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07 23:58 [PATCH 0/2] perf tools: Add MIPS userspace DWARF callchains Ralf Baechle
2015-04-07 23:58 ` [PATCH 1/2] perf tools: Add support for " David Daney
2015-04-08  9:46   ` Jiri Olsa
2015-04-07 23:58 ` [PATCH 2/2] perf tools: Hook up MIPS unwind and dwarf-regs in the Makefile David Daney
2015-04-08  9:58   ` Jiri Olsa [this message]
2015-09-27 16:05 ` [PATCH 0/2] perf tools: Add MIPS userspace DWARF callchains Rabin Vincent
2015-09-27 20:39   ` David Daney
  -- strict thread matches above, loose matches on Subject: below --
2013-05-17 19:00 David Daney
2013-05-17 19:00 ` [PATCH 2/2] perf tools: Hook up MIPS unwind and dwarf-regs in the Makefile David Daney

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=20150408095853.GC14284@krava.redhat.com \
    --to=jolsa@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=david.daney@cavium.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.org \
    /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