From: Ingo Molnar <mingo@kernel.org>
To: Alexei Starovoitov <ast@plumgrid.com>
Cc: davem@davemloft.net, hpa@zytor.com, acme@redhat.com,
acme@infradead.org, torvalds@linux-foundation.org,
rostedt@goodmis.org, akpm@linux-foundation.org,
a.p.zijlstra@chello.nl, linux-kernel@vger.kernel.org,
peterz@infradead.org, jolsa@redhat.com, daniel@iogearbox.net,
masami.hiramatsu.pt@hitachi.com, tglx@linutronix.de,
namhyung@kernel.org, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/core] bpf: Fix the build on BPF_SYSCALL= y && !CONFIG_TRACING kernels, make it more configurable
Date: Thu, 2 Apr 2015 17:47:39 +0200 [thread overview]
Message-ID: <20150402154739.GA11974@gmail.com> (raw)
In-Reply-To: <551D63A0.5010003@plumgrid.com>
* Alexei Starovoitov <ast@plumgrid.com> wrote:
> On 4/2/2015 7:30 AM, tip-bot for Ingo Molnar wrote:
> >Committer: Ingo Molnar <mingo@kernel.org>
> >CommitDate: Thu, 2 Apr 2015 16:28:06 +0200
> >
> >bpf: Fix the build on BPF_SYSCALL=y && !CONFIG_TRACING kernels, make it more configurable
>
> Thanks for the fix.
> I've tried this combination and it was fine, since whole kernel/trace/
> directory is not compiled when !CONFIG_TRACING, but I missed the fact
> that CONFIG_RING_BUFFER=y also enables kernel/trace/ which this ia64
> .config exploited :( I'll add it to my set of configs.
I saw this on x86 as well, but yeah, it was a rare thing.
Thanks,
Ingo
prev parent reply other threads:[~2015-04-02 15:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-e1abf2cc8d5d80b41c4419368ec743ccadbb131e@git.kernel.org>
2015-04-02 15:43 ` [tip:perf/core] bpf: Fix the build on BPF_SYSCALL= y && !CONFIG_TRACING kernels, make it more configurable Alexei Starovoitov
2015-04-02 15:47 ` Ingo Molnar [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=20150402154739.GA11974@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=acme@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ast@plumgrid.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 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.