From: Eric Sandeen <sandeen@sandeen.net>
To: Andrew Morton <akpm@osdl.org>
Cc: Timothy Shimmin <tes@sgi.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
xfs mailing list <xfs@oss.sgi.com>
Subject: Re: [PATCH -mm] rescue large xfs preferred iosize from the inode diet patch
Date: Fri, 22 Sep 2006 18:19:18 -0500 [thread overview]
Message-ID: <45146F76.3010301@sandeen.net> (raw)
In-Reply-To: <20060922161040.609286fa.akpm@osdl.org>
Andrew Morton wrote:
>> So the fix for this is coming soon (and the fix is different from the
>> one above).
>>
>
> eh? Eric's patch is based on -mm, which includes the XFS git tree. If I
> go and merge the inode-diet patches from -mm, XFS gets broken until you
> guys merge the above mystery patch. (I prefer to merge the -mm patches
> after all the git trees have gone, but sometimes maintainers dawdle and I
> get bored of waiting).
>
> Is git://oss.sgi.com:8090/nathans/xfs-2.6 obsolete, or are you hiding stuff
> from me? ;)
>
>
well it's in cvs:
http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_iops.c.diff?r1=text&tr1=1.254&r2=text&tr2=1.253&f=h
but I'm too lazy to check git on a friday evening. :)
Well, sgi-guys, I'll let you sort out which patch you want. Sorry for not
checking cvs first!
-Eric
next prev parent reply other threads:[~2006-09-22 23:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 22:33 [PATCH -mm] rescue large xfs preferred iosize from the inode diet patch Eric Sandeen
2006-09-22 1:03 ` David Chinner
2006-09-22 2:03 ` Timothy Shimmin
2006-09-22 2:23 ` Eric Sandeen
2006-09-22 2:43 ` Eric Sandeen
2006-09-22 6:19 ` David Chinner
2006-09-22 7:50 ` Timothy Shimmin
2006-09-22 23:10 ` Andrew Morton
2006-09-22 23:19 ` Eric Sandeen [this message]
2006-09-22 23:34 ` Andrew Morton
2006-09-25 8:02 ` Timothy Shimmin
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=45146F76.3010301@sandeen.net \
--to=sandeen@sandeen.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tes@sgi.com \
--cc=xfs@oss.sgi.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 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.