On Thu Jun 11, 2026 at 6:46 AM PDT, Steven Rostedt wrote: > On Wed, 10 Jun 2026 08:42:51 -0700 > Alexei Starovoitov <[email protected]> wrote: > >> If my memory doesn't fail me you said it's fine during v1,v2 iterations. > > I'm fine with it, but I wanted to test it first. Did I give an Acked-by? > >> The last v3 - v8 you were silent, so we assumed you're still fine. > > When I see AI reports that say the series needs a fix, I don't bother > looking. I thought that was the entire point of AI; to let the maintainer > not have to review if the AI found something.
AI finds things to consider, but when they're considered and postponned to future it doesn't understand that and keep reporting the same thing every revision. So it might look like that patches are landing with outstanding AI complains, but this is not the case. btw since patches touch ftrace from time to time should we add your ftrace testsuite to bpf CI ? How automated is it? > >> >> While at it, please review Mykyta's set: >> https://patchwork.kernel.org/user/todo/netdevbpf/?series=1096695 >> >> It's also been pending for almost a month now. > > Have a better link? I just get a blank page as "TODO" is set to what I have. Ohh. I meant this set: https://lore.kernel.org/bpf/caef4bzzfjsev3alktwdczf6exocl+eefx+6xa3xgrhbmfo1...@mail.gmail.com/ where you said that you'll think more about it after pto. Would be great to land it now for this merge window, so we have discoverability right now and if better approach comes in the future we can adjust to it later.
