From: Dima Kogan <dima@secretsauce.net>
To: acme@kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] perf: we can now read separate debug-info files based on a build ID
Date: Tue, 27 Oct 2015 19:50:41 -0700 [thread overview]
Message-ID: <87twpb7lku.fsf@secretsauce.net> (raw)
In-Reply-To: <87si6exkpt.fsf@secretsauce.net>
Hi. I'd like to get this merged before I forget about it and then I hit
this bug again at some point in the future. Any comment would be great.
Thanks!
next prev parent reply other threads:[~2015-10-28 2:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 2:47 Dima Kogan
2015-09-16 18:50 ` Dima Kogan
2015-10-28 2:50 ` Dima Kogan [this message]
2015-10-28 12:59 ` Arnaldo Carvalho de Melo
2015-10-29 9:42 ` [tip:perf/core] perf symbols: Fix type error when reading a build-id tip-bot for Dima Kogan
2015-10-29 9:42 ` [tip:perf/core] perf symbols: we can now read separate debug-info files based on a build ID tip-bot for Dima Kogan
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=87twpb7lku.fsf@secretsauce.net \
--to=dima@secretsauce.net \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome