> > > still I can see it on patchworks with Neil being the gatekeeper. > > > > Is your tree out of date? That's not what it shows here, we updated that > > a while ago. > > not as long as this series apparently.. plus maintainers were in copy > and actively reviewing v1/v2/v3 > > but yeah, These patches were developed on top of "ece349ade29 Prepare > v2026.07" when the development started (so before the list was > updated).
Also note the key development branch is now called main not master. > anyway, so what is the next step. resend posting as v5 on top of > v2026.10-x ? Like the kernel probably the latest -rc1 or -next depending on dependencies.
