From: Christoph Hellwig <hch@infradead.org>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, roland@redhat.com,
dsmith@redhat.com, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [patch 2/2] Linux Kernel Markers - Create modpost file
Date: Tue, 4 Dec 2007 19:22:43 +0000 [thread overview]
Message-ID: <20071204192243.GA23609@infradead.org> (raw)
In-Reply-To: <20071204191528.GA31752@Krystal>
On Tue, Dec 04, 2007 at 02:15:28PM -0500, Mathieu Desnoyers wrote:
> Yup. What I would really like is to, at least, get the API stabilised
> for 2.6.24. It that means extracting the API changes from the first
> patch, I could do it. Then we would have plenty of time to discuss the
> multiple probes support.
We don't have a stable API anyway. No need to hurry. The only
markers user submitted to far is my suptrace and I'll happily adjust
APIs when they happen to change.
next prev parent reply other threads:[~2007-12-04 19:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 18:18 [patch 0/2] Linux Kernel Markers updates Mathieu Desnoyers
2007-12-04 18:18 ` [patch 1/2] Linux Kernel Markers - Support Multiple Probes Mathieu Desnoyers
2007-12-04 18:55 ` Christoph Hellwig
2007-12-04 20:03 ` Frank Ch. Eigler
2007-12-04 19:06 ` Andrew Morton
2007-12-04 19:21 ` Mathieu Desnoyers
2007-12-04 19:39 ` Andrew Morton
2007-12-04 19:45 ` Mathieu Desnoyers
2007-12-17 17:40 ` Paul E. McKenney
2007-12-20 14:25 ` Mathieu Desnoyers
2007-12-21 17:18 ` Paul E. McKenney
2007-12-17 18:45 ` Paul E. McKenney
2007-12-20 15:09 ` Mathieu Desnoyers
2007-12-04 18:18 ` [patch 2/2] Linux Kernel Markers - Create modpost file Mathieu Desnoyers
2007-12-04 18:57 ` Christoph Hellwig
2007-12-04 19:10 ` Andrew Morton
2007-12-04 19:15 ` Mathieu Desnoyers
2007-12-04 19:22 ` Christoph Hellwig [this message]
2007-12-04 21:34 ` Roland McGrath
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=20071204192243.GA23609@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dsmith@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=roland@redhat.com \
--cc=sam@ravnborg.org \
/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.