From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 00/10] writeback updates V2
Date: Thu, 16 Dec 2010 10:26:07 +1100 [thread overview]
Message-ID: <20101215232606.GJ9925@dastard> (raw)
In-Reply-To: <20101210084215.259628825@bombadil.infradead.org>
On Fri, Dec 10, 2010 at 03:42:15AM -0500, Christoph Hellwig wrote:
> - add IO_DIRECT per Dave's review comment
> - fix up a commit message as per Dave's review comment
> - add Reviewed-by: tags for Dave's reviews
Christoph, do you want me to add this to my xfs-for-2.6.38 branch so
it is easier to test with all the other pending changes we have for
2.6.38?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-12-15 23:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 8:42 [PATCH 00/10] writeback updates V2 Christoph Hellwig
2010-12-10 8:42 ` [PATCH 01/10] xfs: improve mapping type check in xfs_vm_writepage Christoph Hellwig
2010-12-10 8:42 ` [PATCH 02/10] xfs: remove some dead bio handling code Christoph Hellwig
2010-12-10 8:42 ` [PATCH 03/10] xfs: a few small tweaks for overwrites in xfs_vm_writepage Christoph Hellwig
2010-12-10 8:42 ` [PATCH 04/10] xfs: cleanup the xfs_iomap_write_* helpers Christoph Hellwig
2010-12-10 8:42 ` [PATCH 05/10] xfs: kill xfs_iomap Christoph Hellwig
2010-12-10 8:42 ` [PATCH 06/10] xfs: simplify xfs_map_blocks Christoph Hellwig
2010-12-10 8:42 ` [PATCH 07/10] xfs: remove xfs_probe_cluster Christoph Hellwig
2010-12-10 8:42 ` [PATCH 08/10] xfs: remove the all_bh flag from xfs_convert_page Christoph Hellwig
2010-12-10 8:42 ` [PATCH 09/10] xfs: refactor xfs_vm_writepage Christoph Hellwig
2010-12-10 8:42 ` [PATCH 10/10] xfs: simplify xfs_map_at_offset Christoph Hellwig
2010-12-15 23:26 ` Dave Chinner [this message]
2010-12-16 8:42 ` [PATCH 00/10] writeback updates V2 Christoph Hellwig
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=20101215232606.GJ9925@dastard \
--to=david@fromorbit.com \
--cc=hch@infradead.org \
--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