From: Christoph Hellwig <hch@infradead.org>
To: Brian Foster <bfoster@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 2/2] xfs: hole the inode lock across a full file collapse
Date: Mon, 11 Aug 2014 11:03:45 -0700 [thread overview]
Message-ID: <20140811180345.GB469@infradead.org> (raw)
In-Reply-To: <1407523766-62233-3-git-send-email-bfoster@redhat.com>
Looks good,
Reviewed-by: Christoph Hellwig <hch@lst.de>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-08-11 18:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 18:49 [PATCH 0/2] xfs: for-next file collapse bug fixes Brian Foster
2014-08-08 18:49 ` [PATCH 1/2] xfs: don't log inode unless extent shift makes extent modifications Brian Foster
2014-08-11 18:03 ` Christoph Hellwig
2014-08-08 18:49 ` [PATCH 2/2] xfs: hole the inode lock across a full file collapse Brian Foster
2014-08-11 18:03 ` Christoph Hellwig [this message]
2014-08-13 15:42 ` Brian Foster
2014-08-14 3:11 ` Dave Chinner
2014-08-14 19:09 ` Brian Foster
2014-08-14 22:30 ` Dave Chinner
2014-08-11 21:55 ` [PATCH 0/2] xfs: for-next file collapse bug fixes 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=20140811180345.GB469@infradead.org \
--to=hch@infradead.org \
--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