From: Fengguang Wu <fengguang.wu@intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: "Wangnan (F)" <wangnan0@huawei.com>,
"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, Jiri Olsa <jolsa@kernel.org>,
linux-kernel@vger.kernel.org, sukadev@linux.vnet.ibm.com,
Philip Li <philip.li@intel.com>
Subject: Re: [PATCH v4] perf: bpf: Fix build breakage due to libbpf
Date: Sat, 9 Jan 2016 10:03:20 +0800 [thread overview]
Message-ID: <20160109020320.GB20684@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <20160108134608.GF19314@kernel.org>
Hi Arnaldo,
On Fri, Jan 08, 2016 at 10:46:08AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Jan 08, 2016 at 09:31:46PM +0800, Wangnan (F) escreveu:
> > On 2016/1/8 20:51, Arnaldo Carvalho de Melo wrote:
> > >Em Fri, Jan 08, 2016 at 11:09:35AM +0530, Naveen N. Rao escreveu:
> > >>On 2016/01/07 05:39PM, Arnaldo Carvalho de Melo wrote:
> > >>>Em Thu, Jan 07, 2016 at 12:28:15PM +0530, Naveen N. Rao escreveu:
> > >>>>On 2015/12/17 09:19AM, Arnaldo Carvalho de Melo wrote:
> > >>>>>Em Thu, Dec 17, 2015 at 10:37:14AM +0530, Naveen N. Rao escreveu:
> > >>>>Arnaldo,
> > >>>>Can you please push at least the initial 3 patches of this for v4.4?
> > >>>>Wang Nan has posted v6 here:
> > >>>>http://thread.gmane.org/gmane.linux.kernel/2110626
> > >>>So I tried it again today, from the v6, the latest patch with that
> > >>>subject line in my inbox, and I get this, after applying the first three
> > >>>patches:
>
> > >>>$ make -C tools clean > /dev/null
> > >>>$ make -C tools/perf build-test
> > >>Thanks, and sorry for the slip-up there - I should've caught that.
> > >The important thing is that it gets caught before getting to Ingo, let
> > >alone Linus, but if you get it before me, I'd appreciate as well 8-)
>
> > Is it possible to ask Fengguang Wu to help us adding perf building test
> > in his kbuild testing system?
>
> I was thinking about this yesterday, when, IIRC, a change made by Kan
> Liang (IIRC) to a kernel/events/ file, in the kernel proper, triggered a
> warning about some casts and I got a warning, since I was in the commig
> log CC list.
>
> Since perf is in the kernel sources, and since we have the 'make -C
> tools/perf build-test' harness, that would be really great to have it
> hooked into the 0day bot...
Yes it should be handy to do so.
CC Philip, he's now maintaining the 0day system.
Thanks,
Fengguang
next prev parent reply other threads:[~2016-01-09 2:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 10:50 [PATCH] " Naveen N. Rao
2015-12-14 11:35 ` [PATCH] tools lib bpf: Support libbpf on PowerPC Wang Nan
2015-12-14 11:53 ` [PATCH] perf: bpf: Fix build breakage due to libbpf Wangnan (F)
2015-12-14 15:17 ` Naveen N. Rao
2015-12-14 11:57 ` [PATCH v2] tools lib bpf: Support libbpf on PowerPC Wang Nan
2015-12-14 15:43 ` Naveen N. Rao
2015-12-15 3:35 ` [PATCH v3 0/3] perf build: PowerPC: Fix build breakage due to libbpf Wang Nan
2015-12-15 3:35 ` [PATCH v3 1/3] perf tools: Fix PowerPC native building Wang Nan
2015-12-15 3:35 ` [PATCH v3 2/3] tools: Move Makefile.arch from perf/config to tools/scripts Wang Nan
2015-12-15 3:35 ` [PATCH v3 3/3] perf: bpf: Fix build breakage due to libbpf Wang Nan
2015-12-15 8:49 ` Wangnan (F)
2015-12-15 8:51 ` [PATCH v4] " Wang Nan
2015-12-15 11:40 ` Naveen N. Rao
2015-12-16 19:42 ` Arnaldo Carvalho de Melo
2015-12-17 1:29 ` Wangnan (F)
2015-12-17 5:07 ` Naveen N. Rao
2015-12-17 12:19 ` Arnaldo Carvalho de Melo
2016-01-07 6:58 ` Naveen N. Rao
2016-01-07 16:08 ` Arnaldo Carvalho de Melo
2016-01-07 20:39 ` Arnaldo Carvalho de Melo
2016-01-07 21:23 ` Arnaldo Carvalho de Melo
2016-01-08 1:56 ` Wangnan (F)
2016-01-08 15:52 ` Jiri Olsa
2016-01-08 5:39 ` Naveen N. Rao
2016-01-08 12:51 ` Arnaldo Carvalho de Melo
2016-01-08 13:31 ` Wangnan (F)
2016-01-08 13:46 ` Arnaldo Carvalho de Melo
2016-01-09 2:03 ` Fengguang Wu [this message]
2015-12-15 8:05 ` [PATCH v3 0/3] perf build: PowerPC: " Jiri Olsa
2015-12-15 11:29 ` Naveen N. Rao
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=20160109020320.GB20684@wfg-t540p.sh.intel.com \
--to=fengguang.wu@intel.com \
--cc=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=philip.li@intel.com \
--cc=sukadev@linux.vnet.ibm.com \
--cc=wangnan0@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®