[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAEf4BzYhmauUjfj_peuT3ct9p=p6-Uc2F1LZvgT0+6hY+7Z7RQ@mail.gmail.com>
Date: Mon, 29 Jul 2024 15:07:38 -0700
From: Andrii Nakryiko <andrii.nakryiko@...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>, 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: Fixes tag needs some work in the bpf-next tree
On Mon, Jul 29, 2024 at 2:50 PM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi all,
>
> In commit
>
> 76ea8f9e0003 ("selftests/bpf: Workaround strict bpf_lsm return value check.")
>
> Fixes tag
>
> Fixes: af980eb89f06 ("bpf, lsm: Add check for BPF LSM return value")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Maybe you meant
>
> Fixes: 5d99e198be27 ("bpf, lsm: Add check for BPF LSM return value")
Yes, you are right, I missed updating the sha during bpf-next rebase.
Thanks for the heads up, I just updated and force-pushed the
bpf-next/for-next tag.
>
> --
> Cheers,
> Stephen Rothwell
Powered by blists - more mailing lists