From: Dave Chinner <david@fromorbit.com>
To: Brian Foster <bfoster@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 0/2] xfsprogs/repair: fix a couple large block size alignment issues
Date: Fri, 6 Feb 2015 10:37:21 +1100 [thread overview]
Message-ID: <20150205233720.GV4251@dastard> (raw)
In-Reply-To: <1423173023-54866-1-git-send-email-bfoster@redhat.com>
On Thu, Feb 05, 2015 at 04:50:21PM -0500, Brian Foster wrote:
> Hi all,
>
> This is just a couple fixes for issues I came across while playing with
> larger block and inode sizes on a ppc64 box...
Yup, fixes look sane. I'll test and pull them in.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2015-02-05 23:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 21:50 [PATCH 0/2] xfsprogs/repair: fix a couple large block size alignment issues Brian Foster
2015-02-05 21:50 ` [PATCH 1/2] repair: fix v5 sb ino alignment calculation for large blocksizes Brian Foster
2015-02-05 21:50 ` [PATCH 2/2] repair: check ino alignment value to avoid mod by zero Brian Foster
2015-02-05 23:37 ` Dave Chinner [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=20150205233720.GV4251@dastard \
--to=david@fromorbit.com \
--cc=bfoster@redhat.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