er.kernel.org,
> > linux-e...@vger.kernel.org, a...@linux-foundation.org, hu...@google.com,
> > lczer...@redhat.com
> > Subject: [PATCH v4 00/20] change invalidatepage prototype to accept length
>
> Hi Ted,
>
> you've mentioned that you'll carry the changed in the ext
...@vger.kernel.org, a...@linux-foundation.org, hu...@google.com,
lczer...@redhat.com
Subject: [PATCH v4 00/20] change invalidatepage prototype to accept length
Hi Ted,
you've mentioned that you'll carry the changed in the ext4 tree. Are
you going to take it for the next merge window
om,
> lczer...@redhat.com
> Subject: [PATCH v4 00/20] change invalidatepage prototype to accept length
Hi Ted,
you've mentioned that you'll carry the changed in the ext4 tree. Are
you going to take it for the next merge window ?
However I still need some review on the mm part of the series,
,
lczer...@redhat.com
Subject: [PATCH v4 00/20] change invalidatepage prototype to accept length
Hi Ted,
you've mentioned that you'll carry the changed in the ext4 tree. Are
you going to take it for the next merge window ?
However I still need some review on the mm part of the series,
Andrew, Hugh
Hi,
This set of patches are aimed to allow truncate_inode_pages_range() handle
ranges which are not aligned at the end of the page. Currently it will
hit BUG_ON() when the end of the range is not aligned. Punch hole feature
however can benefit from this ability saving file systems some work not
Hi,
This set of patches are aimed to allow truncate_inode_pages_range() handle
ranges which are not aligned at the end of the page. Currently it will
hit BUG_ON() when the end of the range is not aligned. Punch hole feature
however can benefit from this ability saving file systems some work not
6 matches
Mail list logo
