From: Christoph Hellwig <hch@lst.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Chinner <david@fromorbit.com>,
xfs-masters@oss.sgi.com, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, Jan Kara <jack@suse.cz>,
Christoph Hellwig <hch@lst.de>, Felix Blyakher <felixb@sgi.com>
Subject: Re: linux-next: manual merge of the xfs tree with the ext3 tree
Date: Fri, 4 Sep 2009 01:56:52 +0200 [thread overview]
Message-ID: <20090903235652.GA7674@lst.de> (raw)
In-Reply-To: <20090904095500.04205407.sfr@canb.auug.org.au>
On Fri, Sep 04, 2009 at 09:55:00AM +1000, Stephen Rothwell wrote:
> 218604a0bf712976171798b1dd5c44d26d6d0ea4 ("xfs: Convert sync_page_range()
> to simple filemap_write_and_wait_range()") from the ext3 tree and commit
> 13e6d5cdde0e785aa943810f08b801cadd0935df ("xfs: merge fsync and O_SYNC
> handling") from the xfs tree.
>
> They both do the same thing (to this bit of code) ... I used the version
> from the xfs tree.
Yes, the xfs tree one is the better one, the one in Jan's tree only
does about half of it.
next prev parent reply other threads:[~2009-09-03 23:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 23:55 linux-next: manual merge of the xfs tree with the ext3 tree Stephen Rothwell
2009-09-03 23:56 ` Christoph Hellwig [this message]
2009-09-04 8:11 ` Jan Kara
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=20090903235652.GA7674@lst.de \
--to=hch@lst.de \
--cc=david@fromorbit.com \
--cc=felixb@sgi.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=xfs-masters@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.