From: Jens Axboe <axboe@kernel.dk>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@redhat.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
Tom Zanussi <zanussi@us.ibm.com>,
ltt-dev@shafik.org, Michel Dagenais <michel.dagenais@polymtl.ca>
Subject: Re: [PATCH 10/11] LTTng-core 0.5.108 : relayfs
Date: Thu, 14 Sep 2006 17:59:00 +0200 [thread overview]
Message-ID: <20060914155900.GB5253@kernel.dk> (raw)
In-Reply-To: <20060914155427.GE29906@Krystal>
On Thu, Sep 14 2006, Mathieu Desnoyers wrote:
> * Jens Axboe (axboe@kernel.dk) wrote:
> > On Wed, Sep 13 2006, Mathieu Desnoyers wrote:
> > > 10 - Forward port of RelayFS 2.6.16 API, plus some enhancements.
> > > patch-2.6.17-lttng-core-0.5.108-relayfs.diff
> >
> > One big question - why?!
> >
> (repeated)
> It's a temporary solution only used because relayfs has been such a
> moving target lately that I decided to wait for things to settle down
> before switching. I plan to switch to the new relay.o and use DebugFS
> for filesystem. I just haven't done the change yet.
Since going into the kernel, it's only changed once and that was 6
(something like that) months ago. So I'd say that your statement there
is hugely exaggerated. Just get it fixed up, if you are serious in any
way with posting your patches.
--
Jens Axboe
next prev parent reply other threads:[~2006-09-14 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-14 3:49 [PATCH 10/11] LTTng-core 0.5.108 : relayfs Mathieu Desnoyers
2006-09-14 7:53 ` Jens Axboe
2006-09-14 15:54 ` Mathieu Desnoyers
2006-09-14 15:59 ` Jens Axboe [this message]
2006-09-14 9:58 ` Paul Mundt
2006-09-14 15:56 ` Mathieu Desnoyers
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=20060914155900.GB5253@kernel.dk \
--to=axboe@kernel.dk \
--cc=akpm@osdl.org \
--cc=gregkh@suse.de \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@shafik.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=michel.dagenais@polymtl.ca \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=zanussi@us.ibm.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