From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [GIT PULL] xfs: fixes for 3.15-rc6
Date: Thu, 15 May 2014 22:53:20 -0700 [thread overview]
Message-ID: <20140516055320.GA20975@infradead.org> (raw)
In-Reply-To: <20140516021144.GK5421@dastard>
On Fri, May 16, 2014 at 12:11:44PM +1000, Dave Chinner wrote:
> Hi Linus,
>
> Can you please pull the updates listed below? I found a bunch of
> error sign issues while determine what we need to do to rid XFS of
> this problem permanently. A couple of the bugs are in data integirty
> operations, a couple more are in the new COLLAPSE_RANGE code. One of
> these came in through a recent ext4 merge and so I had to update the
> base tree to 3.15-rc5 before fixing the issues.
Doesn't this miss the log roundin fix?
Linus said he is away for about a weeke anyway, while we're at it.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-05-16 5:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 2:11 [GIT PULL] xfs: fixes for 3.15-rc6 Dave Chinner
2014-05-16 5:53 ` Christoph Hellwig [this message]
2014-05-16 6:01 ` Dave Chinner
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=20140516055320.GA20975@infradead.org \
--to=hch@infradead.org \
--cc=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