---- On Sat, 05 Jul 2025 01:52:58 -0300 Randy Dunlap <rdunlap@xxxxxxxxxxxxx> wrote --- > > > On 7/4/25 9:44 PM, Kumar Kartikeya Dwivedi wrote: > > On Sat, 5 Jul 2025 at 01:38, Randy Dunlap <rdunlap@xxxxxxxxxxxxx> wrote: > >> > >> > >> > >> On 7/4/25 4:35 PM, Randy Dunlap wrote: > >>> > >>> > >>> On 7/4/25 3:51 AM, Stephen Rothwell wrote: > >>>> Hi all, > >>>> > >>>> Changes since 20250703: > >>>> > >>> > >>> on i386: > >>> > >>> kernel/bpf/stream.c: In function 'dump_stack_cb': > >>> kernel/bpf/stream.c:501:53: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] > >>> 501 | (void *)ip, line, file, num); > >>> | ^ > >>> ../kernel/bpf/stream.c:505:64: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] > >>> 505 | ctxp->err = bpf_stream_stage_printk(ctxp->ss, "%pS\n", (void *)ip); > >>> | > >>> > >>> > >> > >> Also reported (earlier) here: > >> > >> https://lore.kernel.org/linux-next/CACo-S-16Ry4Gn33k4zygRKwjE116h1t--DSqJpQfodeVb0ssGA@xxxxxxxxxxxxxx/T/#u > >> > > > > Thanks, I will share a fix soon. Could the bot also Cc the author of > > the commit using git blame? > > I added the email address for the bot. We'll see if it can read email. The bot doesn't know how to read email yet. :) The challenge with Cc the author today is that we don't build every commit or bisect, so we are not able to indentify the culprit commit. It is definitely on our roadmap to do that, but we don't know when such a feature would be available. Best, - Gus
