From: Nathan Scott <nscott@aconex.com>
To: David Chinner <dgc@sgi.com>
Cc: xfs-dev@sgi.com, xfs@oss.sgi.com
Subject: Re: Review: Clear unwritten flag on during partial page truncation
Date: Fri, 22 Dec 2006 09:04:58 +1100 [thread overview]
Message-ID: <1166738698.5572.194.camel@edge> (raw)
In-Reply-To: <20061221113724.GK33919298@melbourne.sgi.com>
On Thu, 2006-12-21 at 22:37 +1100, David Chinner wrote:
> > ...
> > the same lines. But alot of effort, with the possibility of it not
> > being merged at all, as it touches code outside XFS. D'oh.
>
> Yep, pretty much my thinking as well.
>
> I forgot about that hack in xfs_count_page_state() - we should
> be able to remove that with this change, right?
>
Hmm, yes, quite possibly ... worth testing out anyway, but I think
you may be right there.
cheers.
--
Nathan
next prev parent reply other threads:[~2006-12-21 23:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 6:28 Review: Clear unwritten flag on during partial page truncation David Chinner
2006-12-20 8:21 ` Lachlan McIlroy
2006-12-20 9:07 ` David Chinner
2006-12-21 6:16 ` Nathan Scott
2006-12-21 11:37 ` David Chinner
2006-12-21 22:04 ` Nathan Scott [this message]
2006-12-22 13:21 ` Christoph Hellwig
2006-12-23 2:55 ` David 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=1166738698.5572.194.camel@edge \
--to=nscott@aconex.com \
--cc=dgc@sgi.com \
--cc=xfs-dev@sgi.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