From: Randy Dunlap <rdunlap@infradead.org>
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>,
bot@kernelci.org, kernelci@lists.linux.dev
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
bpf@vger.kernel.org
Subject: Re: linux-next: Tree for Jul 4 (kernel/bpf/stream.c)
Date: Fri, 4 Jul 2025 21:52:58 -0700 [thread overview]
Message-ID: <d5136da0-51f9-4359-a283-9075b4992bfb@infradead.org> (raw)
In-Reply-To: <CAP01T77AWoBqDgOPpmmcL5tQFqNa8W3rxBDB+Er0J5rxogCrVA@mail.gmail.com>
On 7/4/25 9:44 PM, Kumar Kartikeya Dwivedi wrote:
> On Sat, 5 Jul 2025 at 01:38, Randy Dunlap <rdunlap@infradead.org> 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@mail.gmail.com/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.
--
~Randy
next prev parent reply other threads:[~2025-07-05 4:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 10:51 linux-next: Tree for Jul 4 Stephen Rothwell
2025-07-04 23:35 ` linux-next: Tree for Jul 4 (kernel/bpf/stream.c) Randy Dunlap
2025-07-04 23:38 ` Randy Dunlap
2025-07-05 4:44 ` Kumar Kartikeya Dwivedi
2025-07-05 4:52 ` Randy Dunlap [this message]
2025-07-07 14:06 ` Gustavo Padovan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d5136da0-51f9-4359-a283-9075b4992bfb@infradead.org \
--to=rdunlap@infradead.org \
--cc=bot@kernelci.org \
--cc=bpf@vger.kernel.org \
--cc=kernelci@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=memxor@gmail.com \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®