From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: move gfs2 tracepoints to inclue/trace/events dir
Date: Fri, 09 Oct 2009 17:05:19 +0100 [thread overview]
Message-ID: <1255104319.6052.558.camel@localhost.localdomain> (raw)
In-Reply-To: <20091009160115.GA2647@redhat.com>
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.
>
> Signed-off-by: Jason Baron <jbaron@redhat.com>
>
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
Steve.
WARNING: multiple messages have this Message-ID (diff)
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: move gfs2 tracepoints to inclue/trace/events dir
Date: Fri, 9 Oct 2009 17:05:19 +0100 [thread overview]
Message-ID: <1255104319.6052.558.camel@localhost.localdomain> (raw)
Message-ID: <20091009160519.mazYFiNxIWDn6YwY0tYKriDrE5tZJV6HzsTiP1N6Qn4@z> (raw)
In-Reply-To: <20091009160115.GA2647@redhat.com>
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.
>
> Signed-off-by: Jason Baron <jbaron@redhat.com>
>
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
Steve.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
WARNING: multiple messages have this Message-ID (diff)
From: Steven Whitehouse <swhiteho@redhat.com>
To: Jason Baron <jbaron@redhat.com>
Cc: cluster-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: move gfs2 tracepoints to inclue/trace/events dir
Date: Fri, 09 Oct 2009 17:05:19 +0100 [thread overview]
Message-ID: <1255104319.6052.558.camel@localhost.localdomain> (raw)
In-Reply-To: <20091009160115.GA2647@redhat.com>
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.
>
> Signed-off-by: Jason Baron <jbaron@redhat.com>
>
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
Steve.
next prev parent reply other threads:[~2009-10-09 16:05 UTC|newest]
Thread overview: 19+ 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 [this message]
2009-10-09 16:05 ` Steven Whitehouse
2009-10-09 16:05 ` [Cluster-devel] " Steven Whitehouse
2009-10-09 16:20 ` Jason Baron
2009-10-09 16:28 ` [Cluster-devel] " Steven Whitehouse
2009-10-09 16:28 ` Steven Whitehouse
2009-10-09 16:28 ` [Cluster-devel] " Steven Whitehouse
2009-10-09 23:45 ` Christoph Hellwig
2009-10-09 23:45 ` Christoph Hellwig
2009-10-12 9:43 ` [Cluster-devel] " Steven Whitehouse
2009-10-12 9:43 ` Steven Whitehouse
2009-10-12 10:00 ` Ingo Molnar
2009-10-12 10:16 ` [Cluster-devel] " Steven Whitehouse
2009-10-12 10:16 ` Steven Whitehouse
2009-10-25 7:50 ` [Cluster-devel] " Christoph Hellwig
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=1255104319.6052.558.camel@localhost.localdomain \
--to=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 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.