Hi Andrew,
Is it possible to get Willy's folios patchset - or at least the core of it -
staged for the next merge window? I'm working on improvements to the local
filesystem caching code and the network filesystem support library and that
involves a lot of dealing with pages - all of which will need to be converted
to the folios stuff. This has the potential to conflict with the changes
Willy's patches make to filesystems. Further, the folios patchset offers some
facilities that make my changes a bit easier - and some changes that make
things a bit more challenging (e.g. page size becoming variable).
Also, is it possible to get the folios patchset in a stable public git branch
that I can base my patches upon?
Thanks,
David
On Mon, 12 Jul 2021 16:43:29 +0100 David Howells <[email protected]> wrote:
> Hi Andrew,
>
> Is it possible to get Willy's folios patchset - or at least the core of it -
> staged for the next merge window? I'm working on improvements to the local
> filesystem caching code and the network filesystem support library and that
> involves a lot of dealing with pages - all of which will need to be converted
> to the folios stuff. This has the potential to conflict with the changes
> Willy's patches make to filesystems. Further, the folios patchset offers some
> facilities that make my changes a bit easier - and some changes that make
> things a bit more challenging (e.g. page size becoming variable).
It's about that time. However there's a discussion at present which
might result in significant renamings, so I'll wait until that has
panned out.
> Also, is it possible to get the folios patchset in a stable public git branch
> that I can base my patches upon?
I guess Willy's tree, but I doubt if the folio patches will be reliably
stable for some time (a few weeks?)
On Tue, Jul 13, 2021 at 07:11:01PM -0700, Andrew Morton wrote:
> > Also, is it possible to get the folios patchset in a stable public git branch
> > that I can base my patches upon?
>
> I guess Willy's tree, but I doubt if the folio patches will be reliably
> stable for some time (a few weeks?)
So, how about I put the 89 patches which I want to merge this merge
window into a git branch which Dave can develop against? Andrew can
pull that branch into mmotm when it's sufficiently settled for his taste.
In order for that to look good in Linus' tree, either Dave can send a
pull request which includes all of the folio patches, or I can send a
pull request early in the merge window (or even before the merge window
opens) which includes those 89 patches.
That would mean the patches wouldn't have Andrew's sign-off on them, but I
could add a R-b from Andrew to all of them if that's the right way to go.