Re: pahole next->master. Was: [PATCH bpf-next v1] selftests/bpf: Guard addr_space_cast code with __BPF_FEATURE_ADDR_SPACE_CAST

[Arnaldo Carvalho de Melo]

On Thu, Oct 23, 2025 at 08:42:34AM -0700, Alexei Starovoitov wrote:
> On Thu, Oct 23, 2025 at 12:50 AM Jiayuan Chen <jiayuan.chen@xxxxxxxxx> wrote:
> > thanks, but version 1.30 didn't work in my tests - even pahole's master branch fails, only the next branch works...
> >

> > It seems that the 'old' pahole parses some kfuncs incorrectly, for example bpf_dynptr_slice().
l
> Alan,
 
> the introduction of the 'next' branch screwed up the workflow for many people.
> Let's remove it and merge everything into master.
> People expect master branch to be the one where active development
> is happening and the source of truth for the latest features.

My bad, I've been away for too long, next is supposed to be with things
for a short while, testing for a few days, for CI consumption, then move
to master, rinse repeat.

I think we should go back to that model.

- Arnaldo