LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Yuehaibing <yuehaibing@huawei.com>
To: <mathieu.poirier@linaro.org>, <suzuki.poulose@arm.com>,
<peterz@infradead.org>, <mingo@redhat.com>, <acme@kernel.org>,
<alexander.shishkin@linux.intel.com>, <jolsa@redhat.com>,
<namhyung@kernel.org>, <arnaldo.melo@gmail.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 0/2] minor fixes for perf cs-etm
Date: Tue, 4 Jun 2019 16:50:17 +0800 [thread overview]
Message-ID: <b5d842f9-3475-2560-2933-9a1984c1641a@huawei.com> (raw)
In-Reply-To: <20190321023122.21332-1-yuehaibing@huawei.com>
Hi,
Friendly ping:
Arnaldo, will you take this serial?
On 2019/3/21 10:31, Yue Haibing wrote:
> From: YueHaibing <yuehaibing@huawei.com>
>
> v2:
> - patch 1 fix commilt log
> - patch 2 use correct Fixes tag
>
> This patch series fixes two issue:
> 1. fix pass-zero-to-ERR_PTR warning
> 2. return correct errcode to upstream callers
>
> YueHaibing (2):
> perf cs-etm: Remove errnoeous ERR_PTR() usage in in
> cs_etm__process_auxtrace_info
> perf cs-etm: return errcode in cs_etm__process_auxtrace_info()
>
> tools/perf/util/cs-etm.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
next prev parent reply other threads:[~2019-06-04 8:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 2:31 Yue Haibing
2019-03-21 2:31 ` [PATCH v2 1/2] perf cs-etm: Remove errnoeous ERR_PTR() usage in cs_etm__process_auxtrace_info Yue Haibing
2019-03-21 16:42 ` Mathieu Poirier
2019-07-17 23:06 ` [tip:perf/urgent] " tip-bot for YueHaibing
2019-03-21 2:31 ` [PATCH v2 2/2] perf cs-etm: return errcode in cs_etm__process_auxtrace_info() Yue Haibing
2019-03-21 16:44 ` Mathieu Poirier
2019-07-17 23:06 ` [tip:perf/urgent] perf cs-etm: Return " tip-bot for YueHaibing
2019-06-04 8:50 ` Yuehaibing [this message]
2019-07-11 14:33 ` [PATCH v2 0/2] minor fixes for perf cs-etm Yuehaibing
2019-07-11 15:46 ` 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=b5d842f9-3475-2560-2933-9a1984c1641a@huawei.com \
--to=yuehaibing@huawei.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=arnaldo.melo@gmail.com \
--cc=jolsa@redhat.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=suzuki.poulose@arm.com \
--subject='Re: [PATCH v2 0/2] minor fixes for perf cs-etm' \
/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
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).