From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Dave Chinner <david@fromorbit.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Christoph Lameter <cl@linux-foundation.org>,
linux-next@vger.kernel.org, Rik van Riel <riel@redhat.com>,
Lachlan McIlroy <lachlan@sgi.com>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: linux-next: slab tree build failure
Date: Mon, 03 Nov 2008 11:38:17 +0200 [thread overview]
Message-ID: <1225705098.22949.11.camel@penberg-laptop> (raw)
In-Reply-To: <20081103051433.GS19509@disturbed>
On Mon, 2008-11-03 at 16:14 +1100, Dave Chinner wrote:
> Yeah, that will work for the moment. It's probably best that we
> don't try to add defrag back into the XFS inode code until we've
> sorted all the niggling problems as a result of the "combine..."
> patch.
OK, I dropped the XFS defrag patch from my tree for now. Thanks guys!
Pekka
next prev parent reply other threads:[~2008-11-03 9:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 4:42 linux-next: slab tree build failure Stephen Rothwell
2008-11-03 5:14 ` Dave Chinner
2008-11-03 9:38 ` Pekka Enberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-06-19 4:16 Stephen Rothwell
2009-06-19 10:40 ` Benjamin Herrenschmidt
2009-06-22 9:09 ` Pekka Enberg
2009-09-07 5:37 Stephen Rothwell
2009-09-07 6:10 ` Pekka Enberg
2009-09-07 7:31 ` Stephen Rothwell
2009-09-07 7:43 ` Pekka Enberg
2009-09-07 8:29 ` Stephen Rothwell
2009-09-07 9:04 ` Heiko Carstens
2009-09-07 9:22 ` Pekka Enberg
2009-09-07 8:35 ` Catalin Marinas
2009-09-08 16:32 ` Luis R. Rodriguez
2009-12-07 4:11 Stephen Rothwell
2009-12-08 3:44 Stephen Rothwell
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=1225705098.22949.11.camel@penberg-laptop \
--to=penberg@cs.helsinki.fi \
--cc=cl@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=lachlan@sgi.com \
--cc=linux-next@vger.kernel.org \
--cc=riel@redhat.com \
--cc=sfr@canb.auug.org.au \
/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