From: Ingo Molnar <mingo@elte.hu>
To: Christoph Hellwig <hch@lst.de>
Cc: Theodore Tso <tytso@mit.edu>,
linux-kernel@vger.kernel.org,
Fr?d?ric Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4/jbd2: remove stray markers
Date: Wed, 6 May 2009 13:58:50 +0200 [thread overview]
Message-ID: <20090506115850.GO25203@elte.hu> (raw)
In-Reply-To: <20090506114415.GA26947@lst.de>
* Christoph Hellwig <hch@lst.de> wrote:
> I was planning to do make sure it's all gone. Once we are into
> the 2.6.31 merge dinwo I fear that the final patches will miss the
> window due to all these interdependencies. But Ingo didn't seem
> to be too interested in taking the other patches that would be
> required for it, so I guess I'll try to somehow get it done in the
> merge window and otherwise we'll have to wait for 2.6.32.
Well, while coupling to lots of subsystems is natural for something
as intrinsic as the tracing tree - still i dont want to over-do it.
In little over a month these patches can go into their local
subsystem trees, without any interactions with anything.
So the patches you did are nice - just (as it is usual with any core
kernel tree) the logistics have to be planned carefully.
Ingo
next prev parent reply other threads:[~2009-05-06 11:59 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 [this message]
2009-05-06 12:55 ` Theodore Tso
2009-05-06 13:18 ` Ingo Molnar
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=20090506115850.GO25203@elte.hu \
--to=mingo@elte.hu \
--cc=fweisbec@gmail.com \
--cc=hch@lst.de \
--cc=linux-ext4@vger.kernel.org \
--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