Re: [PATCH v2 0/1] finalize removing the page pool members in struct page

On 12/18/25 1:17 AM, Byungchul Park wrote:

On Wed, Dec 17, 2025 at 02:43:07PM +0100, Vlastimil Babka wrote:

quoted

On 12/16/25 04:03, Byungchul Park wrote:

quoted

Since this patch requires to use newly introduced APIs in net tree, I've
been waiting for those to be ready in mm tree.  Now that mm tree has
been rebased so as to include the APIs, this patch can be merged to mm
tree.

This patch has been carried out in a separate thread so far for the
reviews [1]:

 [1] https://lore.kernel.org/all/20251119012709.35895-1-byungchul@sk.com/ (local)
---
Changes from v1:
      1. Drop the finalizing patch removing the pp fields of struct
         page since I found that there is still code accessing a pp
         field via struct page.  I will retry the finalizing patch
         after resolving the issue.

Could we just make that necessary change of
drivers/net/ethernet/intel/ice/ice_ethtool.c part of this series and do it
all at once? We're changing both mm and net anyway.

Yes.  That's what I think it'd better do.  1/2 can be merged separately
and Andrew took it.  I'd like to re-post 'ice fix' + 2/2 in a series if
it's allowed.

quoted

Also which tree will carry the series? I assume net will want to, as the

I'm trying to apply changes focused on mm to mm tree, and changes
focused on net to net tree.  However, yeah, it'd make things simpler if
I can go with a single series for mm tree.

I *think* that the ice patch should go via the net-next tree (and
ideally via the iwl tree first). Also it looks like both patches could
cause quite a bit of conflicts, as the page pool code and the ice driver
are touched frequently.

Perhaps the easier/cleaner way to handle this is publishing a stable
branch somewhere based on the most recent common ancestor and let both
the mm and the net-next tree pull from it? Other opinions welcome!

Anyway the net-next tree is and will be closed up to Jan 2.

Cheers,

Paolo