From: Oleg Nesterov <oleg@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: kbuild test robot <fengguang.wu@intel.com>,
kbuild-all@01.org, LKML <linux-kernel@vger.kernel.org>,
Michael Halcrow <mhalcrow@us.ibm.com>,
Tyler Hicks <tyhicks@canonical.com>,
ecryptfs@vger.kernel.org
Subject: Re: [trace:ftrace/core 1/3] include/trace/syscall.h:39:6: error: 'TIF_SYSCALL_TRACEPOINT' undeclared
Date: Thu, 19 Jun 2014 17:06:47 +0200 [thread overview]
Message-ID: <20140619150647.GA7803@redhat.com> (raw)
In-Reply-To: <20140619101016.6f6396df@gandalf.local.home>
On 06/19, Steven Rostedt wrote:
>
> On Wed, 18 Jun 2014 21:15:59 -0400
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > On Thu, 19 Jun 2014 03:25:46 +0800
> > kbuild test robot <fengguang.wu@intel.com> wrote:
> >
> > > tree: git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git ftrace/core
> > > head: 72fa1a896d8ef355e81270667803ceb16a3dd13f
> > > commit: 32def52ce8faec72c353b6304ca98176687e18f1 [1/3] tracing: Fix syscall_*regfunc() vs copy_process() race
> > > config: make ARCH=xtensa allyesconfig
>
> I got a bit confused because I just noticed that the patch does include
> thread_info.h. But then I noticed that TIF_SYSCALL_TRACEPOINT is
> defined in arch/x86/include/asm/thread_info.h, and this is generic
> code. and the error here is for ARCH=xtensa. We can not be using this.
Yes, I was confused the same way.
> Crap, I just sent a pull request to Linus, I'll have to tell him not to
> pull it.
>
> I'll look for other solutions.
Sorry. Please see another email I sent, we probably need
CONFIG_HAVE_SYSCALL_TRACEPOINTS.
Oleg.
next prev parent reply other threads:[~2014-06-19 15:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53a1e7ba.ZIiv6DbOB78b9RzY%fengguang.wu@intel.com>
2014-06-19 1:15 ` [trace:ftrace/core 1/3] include/trace/syscall.h:39:6: error: 'TIF_SYSCALL_TRACEPOINT' undeclared Steven Rostedt
2014-06-19 1:17 ` Steven Rostedt
2014-06-19 1:38 ` Steven Rostedt
2014-06-19 15:03 ` Oleg Nesterov
2014-06-19 15:26 ` Steven Rostedt
2014-06-19 15:51 ` Oleg Nesterov
2014-06-19 16:08 ` Steven Rostedt
2014-06-19 14:10 ` Steven Rostedt
2014-06-19 15:06 ` Oleg Nesterov [this message]
2014-07-03 21:34 ` Tyler Hicks
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=20140619150647.GA7803@redhat.com \
--to=oleg@redhat.com \
--cc=ecryptfs@vger.kernel.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhalcrow@us.ibm.com \
--cc=rostedt@goodmis.org \
--cc=tyhicks@canonical.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