From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: Updated xfsprogs 2.6.38 merge
Date: Tue, 5 Jul 2011 12:48:55 +1000 [thread overview]
Message-ID: <20110705024855.GA561@dastard> (raw)
Folks,
I pushed out an updated 2.6.38 kernel merge to xfsprogs patchset a
couple of days ago. I've been doing quite a bit of testing on it,
both 32 bit and 64 bit, with 512 byte, 1k and 4k block size
filesystems and I haven't come across any regressions. The patchset
can be found here:
git://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev kernel-2.6.38-sync
It's pretty much unchanged from the last set of patches I sent,
except for one minor fix to the radix tree code for an off by one in
the path array size for item and tag deletes.
I'm pretty much ready to commit this update so I can then move
forward with updating it to the 3.0 kernel code base as a smaller
incremental series.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2011-07-05 2:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 2:48 Dave Chinner [this message]
2011-07-10 21:01 ` Updated xfsprogs 2.6.38 merge Christoph Hellwig
2011-07-11 0:01 ` Dave Chinner
2011-07-11 5:27 ` Christoph Hellwig
2011-07-22 15:57 ` Christoph Hellwig
2011-07-29 22:12 ` Alex Elder
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=20110705024855.GA561@dastard \
--to=david@fromorbit.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