[PATCH bpf] cacheinfo: move get_cpu_cacheinfo_id() back out
Jakub Kicinski
kuba at kernel.org
Tue Nov 23 10:37:25 PST 2021
On Tue, 23 Nov 2021 07:45:41 -1000 Song Liu wrote:
> > x86 resctrl folks, does this look okay?
> >
> > I'd like to do some bpf header cleanups in -next which this is blocking.
> > How would you like to handle that? This change looks entirely harmless,
> > can I get an ack and take this via bpf/netdev to Linus ASAP so it
> > propagates to all trees?
>
> Does this patch target the bpf tree, or the bpf-next tree? If we want to unblock
> bpf header cleanup in -next, we can simply include it in a set for bpf-next.
No strong preference. Since this is very much not a bpf patch and
should be safe my intuition is to ship it to Linus ASAP and avoid
any potential conflicts with other -next trees. Also riscv people
may appreciate it getting fixed sooner rather than later. If they
trip up the same dependency later on in the cycle and we've already
committed this patch to bpf-next they'd have to duplicate the patch
in their tree.
More information about the linux-riscv
mailing list