From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: peterz@infradead.org, mingo@redhat.com,
alexander.shishkin@linux.intel.com, namhyung@kernel.org,
yao.jin@linux.intel.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] perf tools: Miscellaneous fix from the previous cycle
Date: Thu, 15 Feb 2018 11:55:12 -0300 [thread overview]
Message-ID: <20180215145512.GC30974@kernel.org> (raw)
In-Reply-To: <1518467557-18505-1-git-send-email-mathieu.poirier@linaro.org>
Em Mon, Feb 12, 2018 at 01:32:34PM -0700, Mathieu Poirier escreveu:
> Good day Arnaldo,
>
> Here are 3 patches that were sent late in the v4.15 cycle, too late for
> you to pick up for the v4.16 cycle. I don't know if they are on a backlog
> of yours somewhere or if you've made a mental note of them - if so kindly
> disregard this set. Otherwise, here they are again, rebased to your latest
> perf/core [1].
>
> All 3 patches are required for proper functionning of the CoreSight
> trace decoding integration that is in the current cycle.
Thanks, applied the 3 patches.
- Arnaldo
WARNING: multiple messages have this Message-ID (diff)
From: acme@kernel.org (Arnaldo Carvalho de Melo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] perf tools: Miscellaneous fix from the previous cycle
Date: Thu, 15 Feb 2018 11:55:12 -0300 [thread overview]
Message-ID: <20180215145512.GC30974@kernel.org> (raw)
In-Reply-To: <1518467557-18505-1-git-send-email-mathieu.poirier@linaro.org>
Em Mon, Feb 12, 2018 at 01:32:34PM -0700, Mathieu Poirier escreveu:
> Good day Arnaldo,
>
> Here are 3 patches that were sent late in the v4.15 cycle, too late for
> you to pick up for the v4.16 cycle. I don't know if they are on a backlog
> of yours somewhere or if you've made a mental note of them - if so kindly
> disregard this set. Otherwise, here they are again, rebased to your latest
> perf/core [1].
>
> All 3 patches are required for proper functionning of the CoreSight
> trace decoding integration that is in the current cycle.
Thanks, applied the 3 patches.
- Arnaldo
next prev parent reply other threads:[~2018-02-15 14:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 20:32 [PATCH 0/3] perf tools: Miscellaneous fix from the previous cycle Mathieu Poirier
2018-02-12 20:32 ` Mathieu Poirier
2018-02-12 20:32 ` [PATCH 1/3] perf tools: Freeing allocated memory Mathieu Poirier
2018-02-12 20:32 ` Mathieu Poirier
2018-02-17 11:28 ` [tip:perf/core] perf cs-etm: " tip-bot for Mathieu Poirier
2018-02-12 20:32 ` [PATCH 2/3] perf util: Use target->per_thread and target->system_wide flags Mathieu Poirier
2018-02-12 20:32 ` Mathieu Poirier
2018-02-17 11:29 ` [tip:perf/core] perf tools: " tip-bot for Jin Yao
2018-02-12 20:32 ` [PATCH 3/3] perf tools: Fixing uninitialised variable Mathieu Poirier
2018-02-12 20:32 ` Mathieu Poirier
2018-02-17 11:29 ` [tip:perf/core] perf auxtrace arm: " tip-bot for Mathieu Poirier
2018-02-15 14:55 ` Arnaldo Carvalho de Melo [this message]
2018-02-15 14:55 ` [PATCH 0/3] perf tools: Miscellaneous fix from the previous cycle Arnaldo Carvalho de Melo
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=20180215145512.GC30974@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=yao.jin@linux.intel.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 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.