From: "Wangnan (F)" <wangnan0@huawei.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: <lizefan@huawei.com>, <pi3orama@163.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/5] perf bpf: Improve error code delivering and output
Date: Wed, 4 Nov 2015 09:43:22 +0800 [thread overview]
Message-ID: <563962BA.1090303@huawei.com> (raw)
In-Reply-To: <20151103154259.GR21609@kernel.org>
On 2015/11/3 23:43, Arnaldo Carvalho de Melo wrote:
> Em Tue, Nov 03, 2015 at 10:44:41AM +0000, Wang Nan escreveu:
>> This patchset is based on tip/core.
>>
>> Arnaldo found some confusing error reports when reviewing BPF related
>> patches. This patch set makes some changes:
> Thanks for working on this!
>
> I applied the first two and made comments about the conversion to using
> err.h, please check,
>
> - Arnaldo
>
I can't find them in your git repository at git.kernel.org. Could you
please recheck?
Thank you.
prev parent reply other threads:[~2015-11-04 1:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 10:44 [PATCH 0/5] perf bpf: Improve error code delivering and output Wang Nan
2015-11-03 10:44 ` [PATCH 1/5] perf test: Keep test result clean if '-v' not set Wang Nan
2015-11-03 11:19 ` Namhyung Kim
2015-11-08 7:27 ` [tip:perf/urgent] " tip-bot for Wang Nan
2015-11-03 10:44 ` [PATCH 2/5] perf tools: Mute libbpf when " Wang Nan
2015-11-03 10:49 ` Wangnan (F)
2015-11-08 7:27 ` [tip:perf/urgent] perf bpf: " tip-bot for Wang Nan
2015-11-03 10:44 ` [PATCH 3/5] perf tools: Parsing libbpf return value using err.h Wang Nan
2015-11-03 15:17 ` Arnaldo Carvalho de Melo
2015-11-03 15:20 ` Arnaldo Carvalho de Melo
2015-11-03 10:44 ` [PATCH 4/5] bpf tools: Improve libbpf error reporting Wang Nan
2015-11-03 10:44 ` [PATCH 5/5] perf tools: Improve BPF related error messages output Wang Nan
2015-11-03 15:43 ` [PATCH 0/5] perf bpf: Improve error code delivering and output Arnaldo Carvalho de Melo
2015-11-04 1:43 ` Wangnan (F) [this message]
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=563962BA.1090303@huawei.com \
--to=wangnan0@huawei.com \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=pi3orama@163.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.