From: Christoph Hellwig <hch@infradead.org>
To: Ofer Heifetz <oferh@marvell.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Andy Poling <andy@realbig.com>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: XFS support for ARMv5
Date: Thu, 26 Nov 2009 09:24:08 -0500 [thread overview]
Message-ID: <20091126142408.GA16517@infradead.org> (raw)
In-Reply-To: <EE71107DF0D1F24FA2D95041E64AB9E8985A59F895@IL-MB01.marvell.com>
On Thu, Nov 26, 2009 at 04:19:39PM +0200, Ofer Heifetz wrote:
> Hi Christoph,
>
> I applied the patches to 2.6.31.6 and the mount passes file. I copied some data to the XFS DOK and had no problem reading the content after several system reset.
>
> Here is a dmesg snippet:
>
> SGI XFS with ACLs, security attributes, large block/inode numbers, no debug enabled
> XFS mounting filesystem sda3
> Starting XFS recovery on filesystem: sda3 (logdev: internal)
> Ending XFS recovery on filesystem: sda3 (logdev: internal)
>
> Is this patch confirmed to be mainlined in 2.6.33?
> I need to know `cos I want to run some data integrity and performance tests on this patch before I merge it.
There's no way to 100% confirm it until it's done, but it's firmly
planned.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-11-26 14:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 12:21 XFS support for ARMv5 oferh
2009-11-18 16:03 ` Eric Sandeen
2009-11-22 16:20 ` Ofer Heifetz
2009-11-22 16:45 ` Richard Sharpe
2009-11-22 20:07 ` Ofer Heifetz
2009-11-22 20:16 ` Richard Sharpe
2009-11-23 15:56 ` Ofer Heifetz
2009-11-22 16:53 ` Eric Sandeen
2009-11-23 14:46 ` Ofer Heifetz
2009-11-25 16:30 ` Andy Poling
2009-11-25 21:06 ` Christoph Hellwig
2009-11-25 22:10 ` Eric Sandeen
2009-11-25 22:29 ` Richard Sharpe
2009-11-26 14:19 ` Ofer Heifetz
2009-11-26 14:24 ` Christoph Hellwig [this message]
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=20091126142408.GA16517@infradead.org \
--to=hch@infradead.org \
--cc=andy@realbig.com \
--cc=oferh@marvell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox