From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Dima Kogan <dima@secretsauce.net>
Cc: linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
David Ahern <dsahern@gmail.com>,
Namhyung Kim <namhyung@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>
Subject: Re: [PATCH 0/2] perf: we can now read separate debug-info files based on a build ID
Date: Wed, 28 Oct 2015 09:59:23 -0300 [thread overview]
Message-ID: <20151028125923.GA18670@kernel.org> (raw)
In-Reply-To: <87twpb7lku.fsf@secretsauce.net>
Em Tue, Oct 27, 2015 at 07:50:41PM -0700, Dima Kogan escreveu:
> Hi. I'd like to get this merged before I forget about it and then I hit
Hey, me too! But you forgot to ask me to :-) I.e. please CC whoever is
listed in the MAINTAINERS file, also please next time use 'git
format-patch' when sending patches, and don't attach the patches, so
that I can use 'git am' on them.
Anyway, thanks for the patches, I am going thru them now.
- Arnaldo
> this bug again at some point in the future. Any comment would be great.
>
> Thanks!
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2015-10-28 12:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 2:47 [PATCH 0/2] perf: we can now read separate debug-info files based on a build ID Dima Kogan
2015-09-16 18:50 ` Dima Kogan
2015-10-28 2:50 ` Dima Kogan
2015-10-28 12:59 ` Arnaldo Carvalho de Melo [this message]
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=20151028125923.GA18670@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=dima@secretsauce.net \
--cc=dsahern@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@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 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.