From: Christoph Hellwig <hch@infradead.org>
To: Brian Foster <bfoster@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 1/4] xfs: debug mode forced buffered write failure
Date: Sat, 5 Mar 2016 10:27:24 -0800 [thread overview]
Message-ID: <20160305182724.GA9171@infradead.org> (raw)
In-Reply-To: <1457102431-5215-2-git-send-email-bfoster@redhat.com>
Looks fine,
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:[~2016-03-05 18:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 14:40 [PATCH v3 0/4] fix up indlen reservations on extent split Brian Foster
2016-03-04 14:40 ` [PATCH 1/4] xfs: debug mode forced buffered write failure Brian Foster
2016-03-05 18:27 ` Christoph Hellwig [this message]
2016-03-04 14:40 ` [PATCH 2/4] xfs: update freeblocks counter after extent deletion Brian Foster
2016-03-04 14:40 ` [PATCH 3/4] xfs: refactor delalloc indlen reservation split into helper Brian Foster
2016-03-04 14:40 ` [PATCH 4/4] xfs: borrow indirect blocks from freed extent when available Brian Foster
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=20160305182724.GA9171@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