All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: Jens Axboe <jens.axboe@oracle.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org,
	Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH] Blktrace : conversion to tracepoint define
Date: Wed, 26 Nov 2008 12:23:51 +0100	[thread overview]
Message-ID: <20081126112351.GA23386@elte.hu> (raw)
In-Reply-To: <20081126112208.GB20601@elte.hu>


* Ingo Molnar <mingo@elte.hu> wrote:

> Moving the tracepoint definitions into blktrace.c consolidates it 
> nicely without cluttering the various block/* files and ties their 
> presence to CONFIG_BLK_DEV_IO_TRACE as well.

hm, the latter is not a good idea: the tracepoints will be undefined 
when the io tracer is disabled - not good. I'll spread them out like 
you did.

	Ingo

  reply	other threads:[~2008-11-26 11:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-26 10:29 linux-next: block tree build failure Stephen Rothwell
2008-11-26 10:42 ` Ingo Molnar
2008-11-26 10:47   ` Jens Axboe
2008-11-26 11:06     ` [PATCH] Blktrace : conversion to tracepoint define Mathieu Desnoyers
2008-11-26 11:22       ` Ingo Molnar
2008-11-26 11:23         ` Ingo Molnar [this message]
2008-11-26 11:27           ` Mathieu Desnoyers
2008-11-26 11:37       ` Ingo Molnar
2008-11-26 11:56         ` Mathieu Desnoyers
2008-11-26 11:16     ` linux-next: block tree build failure Ingo Molnar
2008-11-26 11:20       ` Jens Axboe
2008-11-26 11:28         ` Ingo Molnar
2008-11-26 11:23       ` Mathieu Desnoyers
2008-11-26 11:25         ` Ingo Molnar

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=20081126112351.GA23386@elte.hu \
    --to=mingo@elte.hu \
    --cc=acme@redhat.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-next@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=sfr@canb.auug.org.au \
    /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.