[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAADnVQKVC4NGsEU0X3XJmmCot40Vvik-9KNFU07F=VBF-4UVRQ@mail.gmail.com>
Date: Thu, 11 Jul 2024 16:51:28 -0700
From: Alexei Starovoitov <alexei.starovoitov@...il.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Daniel Borkmann <daniel@...earbox.net>, Alexei Starovoitov <ast@...nel.org>,
Andrii Nakryiko <andrii@...nel.org>, David Miller <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>, 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 Thu, Jul 11, 2024 at 3:36 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi all,
>
> The following commit is also in the net tree as a different commit
> (but the same patch):
>
> 6f130e4d4a5f ("bpf: Fix order of args in call to bpf_map_kvcalloc")
>
> This is commit
>
> af253aef183a ("bpf: fix order of args in call to bpf_map_kvcalloc")
>
> in the net tree.
Argh.
So the fix was applied to bpf-next back in May and the same people
come back to complain in July that it's somehow still broken and must be
fixed in Linus's tree.
So the new patch was applied to bpf and pulled to net
and on the way to Linus now.
We will ffwd bpf-next in a day or so, if git cannot handle it,
we will revert from bpf-next.
Sigh.
Powered by blists - more mailing lists