Re: [PATCH 2/3] bpf: arena: use page_ref_count() instead of page_mapped() in arena_free_pages()

Alexei Starovoitov <[email protected]>
Newsgroups gmane.linux.kernel,gmane.linux.ports.sh.devel,gmane.linux.kernel.bpf,gmane.linux.kernel.mm
Message-ID <CAADnVQJp30BhhB6N3-GxtYmMpaMTaYvGcK9R5=8PxWD6qEXJhA@mail.gmail.com>
On Tue, Apr 28, 2026 at 9:16 AM David Hildenbrand (Arm)
<[email protected]> wrote:
>
> >>>
> >>> Signed-off-by: David Hildenbrand (Arm) <[email protected]>
> >>> ---
> >>>  kernel/bpf/arena.c | 2 +-
> >>
> >> BPF maintainers will probably want to carry this in the BPF tree.
> >> That's fine - please go ahead and add it.  I'll carry a duplicate in
> >> mm.git so it compiles.
> >
> > We cannot carry the same patch in 2 trees.
> > Sooner or later it will create problems for linux-next
> > and issues during merge window if more changes
> > are done in the same area.
> > The only way to share a patch between trees is to
> > create a stable branch and pull it into 2 trees
> > then sha will be the same,
>
> As lack of stable trees was raised a couple of times in the past, once we're
> done with a transition to a fully git-based mm-next workflow [1], we should be
> able to provide stable trees.
>
> [1]
> https://lore.kernel.org/r/[email protected]

Ohh. Thanks for the link. Full git sounds great to me.
Reading the thread it sounds like you guys want to explore
your own way of managing the tree.
If there is interest we can share during lsfmm
how net and bpf trees are maintained from git pov.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.