[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAADnVQLyvv_pYwYbufmxHAxLXa1xVO1khqzX34B5iJi1_91epw@mail.gmail.com>
Date: Mon, 12 Aug 2024 12:48:23 -0700
From: Alexei Starovoitov <alexei.starovoitov@...il.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>, Masami Hiramatsu <mhiramat@...nel.org>
Cc: Daniel Borkmann <daniel@...earbox.net>, Alexei Starovoitov <ast@...nel.org>,
Andrii Nakryiko <andrii@...nel.org>, bpf <bpf@...r.kernel.org>,
Networking <netdev@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patch in the bpf-next tree
On Sun, Aug 11, 2024 at 2:28 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi all,
>
> The following commit is also in Linus Torvalds' tree as a different commit
> (but the same patch):
>
> 1cbe8143fd2f ("bpf: kprobe: Remove unused declaring of bpf_kprobe_override")
>
> This is commit
>
> 0e8b53979ac8 ("bpf: kprobe: remove unused declaring of bpf_kprobe_override")
>
> in Linus' tree.
Masami,
What happened here?
Looks like the discussion was suggesting for Menglong to
send v2, which he did and the patch was clearly targeting bpf-next tree:
[PATCH bpf-next] bpf: kprobe:
Why did you silently apply it ?
No one knew that.
Menglong sent v2 and it was applied to bpf-next :(
Powered by blists - more mailing lists