Re: [PATCH bpf-next v4 0/7] bpf: fix typos and repeated words in comments

[Hemanth Selam <hemanth.selam@gmail.com>]

On Tue, Sep 08, 2026 at 05:53:53AM +0000, bot+bpf-ci@kernel.org wrote:
> CI has tested the following submission:
> Status:     CONFLICT
> Name:       [bpf-next,v4,0/7] bpf: fix typos and repeated words in comments
> PR:         https://github.com/kernel-patches/bpf/pull/13699
>
> Please rebase your submission onto the most recent upstream change and resubmit
> the patch to get it tested again.

I resent this as v4 rebased onto bpf-next in response to the same report
on v3, and it came back CONFLICT again, so I would rather ask than keep
resending the same content.

The series applies cleanly here on all three of:

  bpf-next master                          1b7415bf70be
  kernel-patches/bpf bpf-next_base
  kernel-patches/bpf bpf-next

with git am and no fuzz, all seven patches.

Looking at the pull requests the bot opened, the base branch does not
look like the bpf-next one:

  v2  PR 13680  base bpf_base       head series/1159292=>bpf
  v3  PR 13685  base bpf-net_base   head series/1159712=>bpf-net
  v4  PR 13699  base bpf-net_base   head series/1160154=>bpf-net

and all three report changed_files: 0, which suggests the series is not
being applied rather than that it conflicts with something.

The subject is tagged [PATCH bpf-next v4].  The series does touch
arch/{arm,powerpc,sparc}/net/bpf_jit*, so if the target tree is picked
up from the paths or from the "net:" in some of the patch subjects, that
might be what is sending it to the bpf/net branches.

Is there anything I should change on my side?  Happy to retitle the arch
patches or split them out if that helps the routing.  Otherwise the
content is unchanged from v3 and I would rather not post a v5 just to
retrigger CI.

Thanks,
Hemanth