public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Baron <jbaron@redhat.com>
To: Steven Whitehouse <swhiteho@redhat.com>
Cc: cluster-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: move gfs2 tracepoints to inclue/trace/events dir
Date: Fri, 9 Oct 2009 12:20:51 -0400	[thread overview]
Message-ID: <20091009162051.GB2647@redhat.com> (raw)
In-Reply-To: <1255104319.6052.558.camel@localhost.localdomain>

On Fri, Oct 09, 2009 at 05:05:19PM +0100, Steven Whitehouse wrote:
> Hi,
> 
> On Fri, 2009-10-09 at 12:01 -0400, Jason Baron wrote:
> > hi,
> > 
> > I'd like to move the gfs2 tracepoints to the the common
> > include/trace/events directory along with all of the other trace events.
> > It makes understanding what tracepoints are available easier, and I see
> > no reason why gfs2 should be different. For example, 'ext4.h' is already
> > in the include/trace/events directory.
> > 
> > thanks,
> > 
> > -Jason
> > 
> I've no objection to that, it sounds like a good plan. Should I stick
> this in the GFS2 tree, or would you rather keep it in the trace tree? I
> was thinking probably the GFS2 tree would be better as it reduces the
> chances of any future conflicts.

gfs2 tree works for me.

thanks,

-Jason


  reply	other threads:[~2009-10-09 16:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-09 16:01 move gfs2 tracepoints to inclue/trace/events dir Jason Baron
2009-10-09 16:05 ` Steven Whitehouse
2009-10-09 16:20   ` Jason Baron [this message]
2009-10-09 16:28     ` Steven Whitehouse
2009-10-09 23:45 ` Christoph Hellwig
2009-10-12  9:43   ` Steven Whitehouse
2009-10-12 10:00     ` Ingo Molnar
2009-10-12 10:16       ` Steven Whitehouse
2009-10-25  7:50       ` Christoph Hellwig
2009-10-25 16:29         ` Ingo Molnar
2009-10-12 10:09   ` 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=20091009162051.GB2647@redhat.com \
    --to=jbaron@redhat.com \
    --cc=cluster-devel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swhiteho@redhat.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