xfs
[Top] [All Lists]

Re: [PATCH v3 05/18] xfs: use ->invalidatepage() length argument

To: Lukas Czerner <lczerner@xxxxxxxxxx>
Subject: Re: [PATCH v3 05/18] xfs: use ->invalidatepage() length argument
From: Theodore Ts'o <tytso@xxxxxxx>
Date: Tue, 23 Apr 2013 10:14:42 -0400
Cc: linux-mm@xxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-ext4@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <1365498867-27782-6-git-send-email-lczerner@xxxxxxxxxx>
Mail-followup-to: Theodore Ts'o <tytso@xxxxxxx>, Lukas Czerner <lczerner@xxxxxxxxxx>, linux-mm@xxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-ext4@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx
References: <1365498867-27782-1-git-send-email-lczerner@xxxxxxxxxx> <1365498867-27782-6-git-send-email-lczerner@xxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
On Tue, Apr 09, 2013 at 11:14:14AM +0200, Lukas Czerner wrote:
> ->invalidatepage() aop now accepts range to invalidate so we can make
> use of it in xfs_vm_invalidatepage()
> 
> Signed-off-by: Lukas Czerner <lczerner@xxxxxxxxxx>
> Cc: xfs@xxxxxxxxxxx

To the xfs team,

Since half of this patch series modifies ext4 extensively, and changes
to the other file systems are relatively small, I plan to carry the
invalidatepage patch set in the ext4 tree for the next development
cycle (i.e., not the upcoming merge window, but the next one).  To
that end, it would be great if you take a look at this patch set and
send us an Acked-by signoff.

Thanks!!

                                                - Ted

<Prev in Thread] Current Thread [Next in Thread>