From: Alexey Budankov <alexey.budankov@linux.intel.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] perf: enable compression of record mode trace to save storage space
Date: Mon, 11 Feb 2019 16:59:14 +0300 [thread overview]
Message-ID: <f381506b-c67d-e966-9849-ec48b9275a44@linux.intel.com> (raw)
In-Reply-To: <20190211135245.GB16528@krava>
On 11.02.2019 16:52, Jiri Olsa wrote:
> On Mon, Jan 28, 2019 at 10:02:49AM +0300, Alexey Budankov wrote:
>>
<SNIP>
>> The patch set is for Arnaldo's perf/core repository.
>
> hi,
> got here late and can't apply this anymore.. which revision
> (commit id) is this based on? perf/core is moving real fast
> these days ;-)
>
> based on errors below I suspect u need to rebase anyway :-\
Yes, I will resend shortly.
Thanks,
Alexey
>
> sry for late response
>
> jirka
>
next prev parent reply other threads:[~2019-02-11 13:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 7:02 Alexey Budankov
2019-01-28 7:06 ` [PATCH v2 1/4] feature: realize libzstd check, LIBZSTD_DIR and NO_LIBZSTD defines Alexey Budankov
2019-01-28 7:08 ` [PATCH v2 2/4] perf record: implement -z=<level> and --mmap-flush=<thres> options Alexey Budankov
2019-01-28 7:10 ` [PATCH v2 3/4] perf record: enable runtime trace compression Alexey Budankov
2019-01-28 7:11 ` [PATCH v2 4/4] perf report: support record trace file decompression Alexey Budankov
2019-02-11 13:52 ` [PATCH v2 0/4] perf: enable compression of record mode trace to save storage space Jiri Olsa
2019-02-11 13:59 ` Alexey Budankov [this message]
[not found] <b834df0e-26b5-3f8c-7a43-18f675fb7434@linux.intel.com>
2019-01-29 10:45 ` Arnaldo Carvalho de Melo
2019-01-29 10:53 ` Arnaldo Carvalho de Melo
2019-01-29 11:39 ` Alexey Budankov
2019-01-29 12:13 ` Arnaldo Carvalho de Melo
2019-01-29 16:39 ` Alexey Budankov
2019-01-29 17:25 ` Andi Kleen
2019-02-11 20:17 Alexey Budankov
2019-02-12 12:27 ` Arnaldo Carvalho de Melo
2019-02-12 14:06 ` Alexey Budankov
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=f381506b-c67d-e966-9849-ec48b9275a44@linux.intel.com \
--to=alexey.budankov@linux.intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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