From: Ingo Molnar <mingo@elte.hu>
To: Theodore Tso <tytso@mit.edu>, Christoph Hellwig <hch@lst.de>,
linux-kernel@vger.kernel.org,
Fr?d?ric Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
linux-ext4
Subject: Re: [PATCH] ext4/jbd2: remove stray markers
Date: Wed, 6 May 2009 15:18:24 +0200 [thread overview]
Message-ID: <20090506131824.GB1325@elte.hu> (raw)
In-Reply-To: <20090506125552.GD4964@mit.edu>
* Theodore Tso <tytso@mit.edu> wrote:
> On Wed, May 06, 2009 at 01:44:15PM +0200, Christoph Hellwig wrote:
> > On Wed, May 06, 2009 at 07:40:51AM -0400, Theodore Tso wrote:
> > > My complaint with Cristoph's
> >
> > Christoph, still :)
>
> Sorry, I keep making that mistake! Keep calling me on it, and
> eventually I'll reprogram those finger macros. :-)
>
>
> > Also without Steve's updates you can't actually use them in a module.
>
> Yep; not sure *how* critical that would be for -next, though.
> Probably there would be some complaints....
>
> In any case, it'll be less work to worry about patch conflicts if
> we just do it during the merge window. If we can just arrange to
> push the tip/tracing changes early, I'll push the marker
> replacement patches as soon as I see them hit mainline.
Cool, thanks! I'll try to aim for an early merge of the tracing
tree. (And such dependent patches are generally possible shortly
after -rc1 as well, especially if the clean-up factor is
significant.)
Ingo
next prev parent reply other threads:[~2009-05-06 13:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 10:44 [PATCH] ext4/jbd2: remove stray markers Christoph Hellwig
2009-05-06 11:03 ` Ingo Molnar
2009-05-06 11:07 ` Christoph Hellwig
2009-05-06 11:12 ` Ingo Molnar
2009-05-06 11:40 ` Theodore Tso
2009-05-06 11:44 ` Christoph Hellwig
2009-05-06 11:58 ` Ingo Molnar
2009-05-06 12:55 ` Theodore Tso
2009-05-06 13:18 ` Ingo Molnar [this message]
2009-05-06 11:54 ` 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=20090506131824.GB1325@elte.hu \
--to=mingo@elte.hu \
--cc=fweisbec@gmail.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tytso@mit.edu \
/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