public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 0/2] [GIT PULL] tracing/events/ring-buffer: block trace points and fix
Date: Wed, 10 Jun 2009 09:28:42 +0800	[thread overview]
Message-ID: <4A2F0C4A.8020109@cn.fujitsu.com> (raw)
In-Reply-To: <20090609234655.GA24118@elte.hu>

Ingo Molnar wrote:
> * Steven Rostedt <rostedt@goodmis.org> wrote:
> 
>> Ingo,
>>
>> Please pull the latest tip/tracing/ftrace tree, which can be found at:
>>
>>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
>> tip/tracing/ftrace
>>
>>
>> Li Zefan (1):
>>       tracing/events: convert block trace points to TRACE_EVENT()
>>
>> Steven Rostedt (1):
>>       ring-buffer: fix ret in rb_add_time_stamp
>>
>> ----
>>  block/blk-core.c             |   16 +-
>>  block/elevator.c             |    8 +-
>>  drivers/md/dm.c              |    5 +-
>>  fs/bio.c                     |    3 +-
>>  include/linux/blktrace_api.h |   13 ++
>>  include/trace/block.h        |   76 -------
>>  include/trace/events/block.h |  483 ++++++++++++++++++++++++++++++++++++++++++
>>  kernel/trace/Makefile        |    5 +-
>>  kernel/trace/blktrace.c      |   78 +++++++-
>>  kernel/trace/ring_buffer.c   |    2 +-
>>  mm/bounce.c                  |    5 +-
>>  11 files changed, 589 insertions(+), 105 deletions(-)
> 
> I'm getting some build failures here:
> 
> In file included from mm/highmem.c:30:
> include/linux/blktrace_api.h:223: warning: ‘struct request’ declared inside parameter list
> include/linux/blktrace_api.h:223: warning: its scope is only this definition or declaration, which is probably not what you want
> include/linux/blktrace_api.h: In function ‘blk_cmd_buf_len’:
> include/linux/blktrace_api.h:225: error: implicit declaration of function ‘blk_pc_request’
> include/linux/blktrace_api.h:225: error: dereferencing pointer to incomplete type
> include/linux/blktrace_api.h: At top level:
> include/linux/blktrace_api.h:228: warning: ‘struct request’ declared inside parameter list
> include/linux/blktrace_api.h:230: warning: ‘struct request’ declared inside parameter list
> distcc[15629] ERROR: compile mm/highmem.c on a/32 failed
> 

I've fixed it. I'll post a new version after I've done some
more building tests.



  reply	other threads:[~2009-06-10  1:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09 16:36 [PATCH 0/2] [GIT PULL] tracing/events/ring-buffer: block trace points and fix Steven Rostedt
2009-06-09 16:36 ` [PATCH 1/2] ring-buffer: fix ret in rb_add_time_stamp Steven Rostedt
2009-06-09 16:36 ` [PATCH 2/2] tracing/events: convert block trace points to TRACE_EVENT() Steven Rostedt
2009-06-09 18:24   ` Steven Rostedt
2009-06-09 17:34 ` [PATCH 0/2] [GIT PULL] tracing/events/ring-buffer: block trace points and fix Steven Rostedt
2009-06-09 23:46 ` Ingo Molnar
2009-06-10  1:28   ` Li Zefan [this message]
2009-06-10  1:30     ` Ingo Molnar
2009-06-10  1:31     ` Steven Rostedt
2009-06-10  1:36       ` Li Zefan
2009-06-10  1:41         ` Steven Rostedt
2009-06-10  1:49           ` Li Zefan
2009-06-10  2:06             ` [PATCH] tracing/events: convert block trace points to TRACE_EVENT(), fix Li Zefan
2009-06-10  2:50               ` Steven Rostedt
2009-06-10  2:56                 ` Li Zefan
2009-06-10  9:57               ` [tip:tracing/core] tracing/events: convert block trace points to TRACE_EVENT(), fix !CONFIG_BLOCK tip-bot for Li Zefan

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=4A2F0C4A.8020109@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox