[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<MEYP282MB23129F39F3031D956B66E66FC6362@MEYP282MB2312.AUSP282.PROD.OUTLOOK.COM>
Date: Tue, 3 Dec 2024 14:42:40 +0800
From: Levi Zim <rsworktech@...look.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: John Fastabend <john.fastabend@...il.com>,
Jakub Sitnicki <jakub@...udflare.com>, "David S. Miller"
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Paolo Abeni <pabeni@...hat.com>, Simon Horman <horms@...nel.org>,
David Ahern <dsahern@...nel.org>, netdev@...r.kernel.org,
bpf@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net 0/2] Fix NPE discovered by running bpf kselftest
On 2024-12-03 07:04, Jakub Kicinski wrote:
> On Sat, 30 Nov 2024 21:38:21 +0800 Levi Zim via B4 Relay wrote:
>> net/core/skmsg.c | 5 +++--
>> net/ipv4/tcp_bpf.c | 8 ++++----
> Haven't looked at the code, but these files are BPF related.
> I'll reassign the patch to BPF maintainers, and please use "PATCH bpf"
> instead of "PATCH net" for next revisions.
Sorry for sending the patch using a wrong prefix. I will use bpf prefix
for next revisions.
I am getting started with bpf development in the kernel.
Initially I thought about using bpf prefix but I saw all the files I
touched are under net which
confuses me about what prefix I should use.
Powered by blists - more mailing lists