Cluster-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 10/18] gfs2: Provide config option for enabling trace points
Date: Wed, 24 Mar 2010 11:20:57 +0000	[thread overview]
Message-ID: <1269429657.2350.1.camel@localhost> (raw)
In-Reply-To: <1269388565.5363.380.camel@localhost>

Hi,

On Tue, 2010-03-23 at 19:56 -0400, Steven Rostedt wrote:
> On Tue, 2010-03-23 at 12:01 +0000, Steven Whitehouse wrote:
> > Hi,
> > 
> > Now in the GFS2 -nmw git tree. Thanks,
> > 
> 
> Note, this depends on patch 1 which we have not yet determined if it
> should be applied or not.
> 
> -- Steve
> 
Sorry, I think I misread the initial message. I can roll it out again if
required. I did a compile test in both states though and it seemed to
work for me,

Steve.




      parent reply	other threads:[~2010-03-24 11:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1269304340-25372-1-git-send-email-jack@suse.cz>
2010-03-23  0:32 ` [Cluster-devel] [PATCH 10/18] gfs2: Provide config option for enabling trace points Jan Kara
2010-03-23 12:01   ` Steven Whitehouse
     [not found]     ` <1269388565.5363.380.camel@localhost>
2010-03-24 11:20       ` Steven Whitehouse [this message]

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=1269429657.2350.1.camel@localhost \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox