linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kim Phillips <kim.phillips@arm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: "Christian Hansen (chansen3)" <chansen3@cisco.com>,
	"linux-perf-users@vger.kernel.org"
	<linux-perf-users@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
	<linux-kernel@vger.kernel.org>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	"Vuille, Martin (Martin)" <vmartin@avaya.com>,
	Martin Vuille <jpmv27@aim.com>
Subject: Re: [PATCH] perf tools arm64: Add libdw DWARF post unwind support for ARM64
Date: Fri, 9 Mar 2018 12:07:20 -0600	[thread overview]
Message-ID: <20180309120720.9358515dbff3b1d1fdf70cc8@arm.com> (raw)
In-Reply-To: <20180309150627.GB8347@kernel.org>

On Fri, 9 Mar 2018 12:06:27 -0300
Arnaldo Carvalho de Melo <acme@kernel.org> wrote:

Hi Arnaldo,

> Em Thu, Mar 08, 2018 at 09:10:30PM -0600, Kim Phillips escreveu:
> > Based on prior work:
> > 
> > https://lkml.org/lkml/2014/5/6/395
> 
> Thanks, looks good, applying.
> 
> Jean, is everything ok with you on this?

By now your email to Jean should have bounced with "The email account
that you tried to reach does not exist."  Removing Jean from Cc.

It seems like you're applying patches.  There are a couple that have
slipped through the cracks: Can you please take a look at applying them?

- "perf tools: Fixing uninitialised variable"
  https://patchwork.kernel.org/patch/10179381/

- "perf unwind: Report error from dwfl_attach_state"
  https://patchwork.kernel.org/patch/10211483/
  [Martin, I guess it would help if you replied-all that patch and
   added your signed-off-by.]

- "perf unwind: Unwind with libdw doesn't take symfs into account"
  https://patchwork.kernel.org/patch/10211599/

Thanks,

Kim

  reply	other threads:[~2018-03-09 18:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <A5E405FE-1BA3-46FC-9A43-CF19A4B369C5@cisco.com>
     [not found] ` <20180226142726.cd413c792d0782f77b60a23e@arm.com>
     [not found]   ` <20180226174040.6998bd3c0a79b2f19c491e4d@arm.com>
     [not found]     ` <9B701F46-6AEA-48D8-9103-71D35C83776D@cisco.com>
2018-03-09  3:10       ` [PATCH] perf tools arm64: Add libdw DWARF post unwind support for ARM64 Kim Phillips
2018-03-09 15:06         ` Arnaldo Carvalho de Melo
2018-03-09 18:07           ` Kim Phillips [this message]
2018-03-09 18:24             ` Arnaldo Carvalho de Melo
2018-03-09 18:49               ` Martin Vuille
2018-03-09 19:15                 ` Kim Phillips
2018-03-09 19:17                   ` Martin Vuille
2018-03-09 19:29                 ` Arnaldo Carvalho de Melo
2018-03-09 19:35                   ` Martin Vuille
2018-03-13 15:23               ` Martin Vuille
2018-03-20  6:20         ` [tip:perf/core] " tip-bot for Kim Phillips

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=20180309120720.9358515dbff3b1d1fdf70cc8@arm.com \
    --to=kim.phillips@arm.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=chansen3@cisco.com \
    --cc=jolsa@redhat.com \
    --cc=jpmv27@aim.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=vmartin@avaya.com \
    /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).