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.ports.sh.devel,gmane.linux.kernel,gmane.linux.kernel.bpf,gmane.linux.kernel.mm |
|---|---|
| Message-ID | <CAADnVQKN_6fCMnv2OC3at4X1v=vuah+_LrwW2PQUYkVXqqVGVQ@mail.gmail.com> |
On Mon, Apr 27, 2026 at 4:15 PM Andrew Morton <[email protected]> wrote: > > On Mon, 27 Apr 2026 16:00:59 +0100 Alexei Starovoitov <[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. > > Git is fine with that. > > > 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, > > For a single one-line patch? Number of changed lines is irrelevant. If there will be a commit on top that moves this line or lines within the hunk, git will be confused depending on order of pulls. We learned this lesson the hard way.