From: Martin KaFai Lau <martin.lau@linux.dev> Date: 2026-05-29 20:40:09
From: Martin KaFai Lau <martin.lau@kernel.org>
I am making a life change and will take a long break
from my current work, so I will step down from the "M:" responsibility.
I am currently a "R:" in "BPF [GENERAL]", this part stays unchanged.
I am folding most of the parts into "BPF [GENERAL]".
For "BPF [BTF]", it is long overdue as I am no longer involved.
It is folded into the "BPF [GENERAL]".
The "BPF [STORAGE & CGROUPS]" will also be covered by "BPF [GENERAL]".
For struct_ops, its usage is no longer limited to networking,
so this naturally should move back to "BPF [GENERAL]".
For the reuseport, it will continue to be maintained together
by "BPF [GENERAL]" and the "NETWORKING [SOCKETS]".
For other "BPF [NETWORKING]...", I am moving myself to "R:".
Thanks!
Signed-off-by: Martin KaFai Lau <martin.lau@kernel.org>
---
MAINTAINERS | 24 +-----------------------
1 file changed, 1 insertion(+), 23 deletions(-)
From: Daniel Borkmann <daniel@iogearbox.net> Date: 2026-05-29 22:27:00
On 5/29/26 10:39 PM, Martin KaFai Lau wrote:
From: Martin KaFai Lau <martin.lau@kernel.org>
I am making a life change and will take a long break
from my current work, so I will step down from the "M:" responsibility.
I am currently a "R:" in "BPF [GENERAL]", this part stays unchanged.
I am folding most of the parts into "BPF [GENERAL]".
For "BPF [BTF]", it is long overdue as I am no longer involved.
It is folded into the "BPF [GENERAL]".
The "BPF [STORAGE & CGROUPS]" will also be covered by "BPF [GENERAL]".
For struct_ops, its usage is no longer limited to networking,
so this naturally should move back to "BPF [GENERAL]".
For the reuseport, it will continue to be maintained together
by "BPF [GENERAL]" and the "NETWORKING [SOCKETS]".
For other "BPF [NETWORKING]...", I am moving myself to "R:".
Thanks!
Signed-off-by: Martin KaFai Lau <martin.lau@kernel.org>
Thanks a ton for all the hard work over the years, Martin! We
hope to see you around, enjoy the break! :-)
Acked-by: Daniel Borkmann <daniel@iogearbox.net>
From: Jason Xing <hidden> Date: 2026-05-30 01:36:27
On Sat, May 30, 2026 at 4:40 AM Martin KaFai Lau [off-list ref] wrote:
From: Martin KaFai Lau <martin.lau@kernel.org>
I am making a life change and will take a long break
from my current work, so I will step down from the "M:" responsibility.
Thanks Martin for your great effort! I always appreciate your awesome
involvement in BPF timestamping!
I am currently a "R:" in "BPF [GENERAL]", this part stays unchanged.
I am folding most of the parts into "BPF [GENERAL]".
For "BPF [BTF]", it is long overdue as I am no longer involved.
It is folded into the "BPF [GENERAL]".
The "BPF [STORAGE & CGROUPS]" will also be covered by "BPF [GENERAL]".
For struct_ops, its usage is no longer limited to networking,
so this naturally should move back to "BPF [GENERAL]".
Maybe it's not an appropriate timing to ask this, but considering the
further development I really want to know if you'll continue with the
latest series around struct_ops? Or you will delegate someone to take
over your work?
Thanks,
Jason
quoted hunk
For the reuseport, it will continue to be maintained together
by "BPF [GENERAL]" and the "NETWORKING [SOCKETS]".
For other "BPF [NETWORKING]...", I am moving myself to "R:".
Thanks!
Signed-off-by: Martin KaFai Lau <martin.lau@kernel.org>
---
MAINTAINERS | 24 +-----------------------
1 file changed, 1 insertion(+), 23 deletions(-)
From: Martin KaFai Lau <martin.lau@linux.dev> Date: 2026-05-30 02:57:48
On Sat, May 30, 2026 at 09:35:47AM +0800, Jason Xing wrote:
Maybe it's not an appropriate timing to ask this, but considering the
further development I really want to know if you'll continue with the
latest series around struct_ops? Or you will delegate someone to take
over your work?
From: Jason Xing <hidden> Date: 2026-05-30 03:32:40
On Sat, May 30, 2026 at 10:57 AM Martin KaFai Lau [off-list ref] wrote:
On Sat, May 30, 2026 at 09:35:47AM +0800, Jason Xing wrote:
quoted
Maybe it's not an appropriate timing to ask this, but considering the
further development I really want to know if you'll continue with the
latest series around struct_ops? Or you will delegate someone to take
over your work?
From: Martin KaFai Lau<martin.lau@kernel.org>
I am making a life change and will take a long break
from my current work, so I will step down from the "M:" responsibility.
I am currently a "R:" in "BPF [GENERAL]", this part stays unchanged.
I am folding most of the parts into "BPF [GENERAL]".
For "BPF [BTF]", it is long overdue as I am no longer involved.
It is folded into the "BPF [GENERAL]".
The "BPF [STORAGE & CGROUPS]" will also be covered by "BPF [GENERAL]".
For struct_ops, its usage is no longer limited to networking,
so this naturally should move back to "BPF [GENERAL]".
For the reuseport, it will continue to be maintained together
by "BPF [GENERAL]" and the "NETWORKING [SOCKETS]".
For other "BPF [NETWORKING]...", I am moving myself to "R:".
Thanks!
Thank you Martin, and best wishes for your long break.
I really appreciate all your guidance and help over the years.
My first kernel commit was guided by you, and I am still very grateful
for that.
Thanks again, and take care!
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov [off-list ref]:
On Fri, 29 May 2026 13:39:09 -0700 you wrote:
From: Martin KaFai Lau <martin.lau@kernel.org>
I am making a life change and will take a long break
from my current work, so I will step down from the "M:" responsibility.
I am currently a "R:" in "BPF [GENERAL]", this part stays unchanged.
I am folding most of the parts into "BPF [GENERAL]".
[...]