On Thu, Mar 9, 2023 at 10:50 AM Daniel Borkmann <daniel@xxxxxxxxxxxxx> wrote: > > On 3/9/23 6:31 PM, Jesus Sanchez-Palencia wrote: > > On Thu, Mar 9, 2023 at 9:27 AM Andrii Nakryiko > > <andrii.nakryiko@xxxxxxxxx> wrote: > >> On Thu, Mar 9, 2023 at 8:06 AM Jesus Sanchez-Palencia > >> <jesussanp@xxxxxxxxxx> wrote: > >>> On Wed, Mar 8, 2023 at 5:40 PM <patchwork-bot+netdevbpf@xxxxxxxxxx> wrote: > >>>> > >>>> Hello: > >>>> > >>>> This patch was applied to bpf/bpf-next.git (master) > >>>> by Andrii Nakryiko <andrii@xxxxxxxxxx>: > >>> > >>> Andrii, are you planning to send this patch to 6.3-rc* since the build > >>> is broken there? > >>> Just double-checking since it was applied to bpf-next. > >> > >> I didn't intend to, feel free to do that. > > > > Oh I always thought that fixes for the rc-* iterations had to come > > from the maintainer > > trees. Should I just send it to lkml directly? > > > >> But just curious, why are you building libbpf from kernel sources > >> instead of Github repo? Is it through perf build? > > > > Yes, through the perf build. We build it altogether as part of our kernel build. > > Ok, just moved over to bpf tree in that case where it will land in -rc's. > Thanks, Daniel, for taking care of this! > Thanks, > Daniel
