Re: [PATCH dwarves v4 0/3] btf_encoder: refactor emission of BTF funcs

[Arnaldo Carvalho de Melo <acme@kernel.org>]

On Thu, Nov 13, 2025 at 09:20:44AM -0800, Alexei Starovoitov wrote:
> On Thu, Nov 13, 2025 at 8:37 AM Alan Maguire <alan.maguire@oracle.com> wrote:
> >
> > On 06/11/2025 01:28, Ihor Solodrai wrote:
> > > This series refactors a few functions that handle how BTF functions
> > > are emitted.
> > >
> > > v3->v4: Error handling nit from Eduard
> > > v2->v3: Add patch removing encoder from btf_encoder_func_state
> > >
> > > v3: https://lore.kernel.org/dwarves/20251105185926.296539-1-ihor.solodrai@linux.dev/
> > > v2: https://lore.kernel.org/dwarves/20251104233532.196287-1-ihor.solodrai@linux.dev/
> > > v1: https://lore.kernel.org/dwarves/20251029190249.3323752-2-ihor.solodrai@linux.dev/
> > >
> >
> > series applied to the next branch of
> > https://git.kernel.org/pub/scm/devel/pahole/pahole.git/
> 
> Same rant as before...
> Can we please keep it normal with all changes going to master ?
> This 'next' branch confused people in the past.

I think the problem before was that it sat there for far too long.

I see value in it staying there for a short period for some eventual
rebase and for some CI thing, to avoid polluting, think of it as some
topic branch on the way to master.

- Arnaldo

> I see no value in this 'next' thing.
> All development should happen in master and every developer
> should base their changes on top of it.
> Eventually the release happens out of master too when it's deemed stable.